Triple
T26723762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CA 905 |
E673777
|
entity |
| Predicate | terminusEastCity |
P3569
|
FINISHED |
| Object | Tijuana |
—
|
NE NERFINISHED |
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: Tijuana | Statement: [CA 905, terminusEastCity, Tijuana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusEastCity Context triple: [CA 905, terminusEastCity, Tijuana]
-
A.
terminusEast
chosen
Indicates that one entity serves as the eastern endpoint or final stop of another entity, such as a route, line, or path.
-
B.
terminusCity
Indicates that a transportation route or service ends or has its final stop in a particular city.
-
C.
terminusCitySoutheast
Indicates that something serves as the southeastern terminus or endpoint of a route, line, or connection in a particular city.
-
D.
terminusCityWest
Indicates that a route, line, or service has its western terminus located in the specified city.
-
E.
terminusCitySouth
Indicates that something serves as the southern terminus or endpoint located in a particular city.
- 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_69eecda481d08190aea69f2f7c745f56 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 3:41 a.m.