Triple
T31268824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TAQ |
E797326
|
entity |
| Predicate | relatedTransportHub |
P207392
|
FINISHED |
| Object | Tasqueña light rail terminal |
E797328
|
NE 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: Tasqueña light rail terminal | Statement: [TAQ, relatedTransportHub, Tasqueña light rail terminal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedTransportHub Context triple: [TAQ, relatedTransportHub, Tasqueña light rail terminal]
-
A.
transportHubType
Indicates the specific category or kind of transport hub associated with an entity (e.g., airport, train station, bus terminal).
-
B.
transportationRelatedTo
Indicates a relationship where one entity is connected to another through transportation, such as serving as a means, mode, infrastructure, or service for moving people or goods.
-
C.
transportationHubType
Indicates the specific kind of transportation hub an entity is (e.g., airport, train station, bus terminal).
-
D.
transportationLinksTo
Indicates that there is a transportation connection or route enabling movement or travel between the two entities.
-
E.
transportHubScope
Indicates the extent or range of areas, routes, or services that a particular transport hub covers or connects.
- F. None of above. chosen
Provenance (5 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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2a72013fd081908d8c23fa15052c3c |
completed | June 11, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 9:13 p.m.