Triple
T33958984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DFW Airport Skylink |
E870655
|
entity |
| Predicate | travelTimeFullLoop |
P103916
|
FINISHED |
| Object | about 18 minutes |
—
|
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: about 18 minutes | Statement: [DFW Airport Skylink, travelTimeFullLoop, about 18 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelTimeFullLoop Context triple: [DFW Airport Skylink, travelTimeFullLoop, about 18 minutes]
-
A.
showRouteDuration
Indicates that an entity displays or provides the duration required to traverse a specific route.
-
B.
timeToTravelEndToEnd
chosen
Indicates the duration required to traverse from the starting point to the ending point of something (e.g., a route, path, or system) without interruption.
-
C.
totalRouteLength
Indicates the overall distance or length of an entire route when all its segments are combined.
-
D.
travelTimeCategory
Indicates the qualitative classification of how long a given travel or trip duration is (e.g., short, medium, long).
-
E.
travelTimeAdvantage
Indicates that one option provides a shorter or more favorable travel time compared to another.
- 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_69f3499c2d7481909c953a5010227725 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 1:49 a.m.