Triple
T33958982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DFW Airport Skylink |
E870655
|
entity |
| Predicate | averageWaitTime |
P177967
|
FINISHED |
| Object | about 2 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 2 minutes | Statement: [DFW Airport Skylink, averageWaitTime, about 2 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: averageWaitTime Context triple: [DFW Airport Skylink, averageWaitTime, about 2 minutes]
-
A.
queueWaitingTimeMaximum
Indicates the maximum amount of time an entity is allowed or expected to wait in a queue before being served or processed.
-
B.
queueLength
Indicates the current number of items or entities waiting in a queue.
-
C.
agingTimeMaximum
Indicates the maximum duration for which something is allowed or expected to age before it is considered expired, mature, or no longer valid.
-
D.
agingTimeMinimum
Indicates the minimum amount of time that must elapse for something to be considered aged or matured according to a specified standard.
-
E.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
- F. None of above. chosen
Provenance (4 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_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f7064d37388190993b2a7305a02b9f |
completed | May 3, 2026, 8:24 a.m. |
Created at: May 1, 2026, 1:49 a.m.