Triple
T36775100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ECT |
E908593
|
entity |
| Predicate | usedInTransportationSchedules |
P21407
|
FINISHED |
| Object | yes |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: yes | Statement: [ECT, usedInTransportationSchedules, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInTransportationSchedules Context triple: [ECT, usedInTransportationSchedules, yes]
-
A.
isUsedInTransportTimetables
chosen
Indicates that something is employed or referenced within transport timetables or schedules.
-
B.
usedForRailwayTimetables
Indicates that something is employed in the creation, organization, or presentation of railway timetables.
-
C.
usedByTransitSystem
Indicates that something is utilized or operated by a transit or public transportation system.
-
D.
usedOnDepartureBoards
Indicates that something (such as a name, code, or label) is the form that is shown on departure boards to represent a service or destination.
-
E.
usedAsTransitRouteFor
Indicates that something serves as a pathway or channel through which another entity is transported or moved.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76e798aa08190ace31098d1b13e9f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff1a972bf08190860696ffcd887c0f |
completed | May 9, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69ff184005d88190bf38283ebc499b28 |
completed | May 9, 2026, 11:19 a.m. |
Created at: May 3, 2026, 4:12 p.m.