Triple
T19174527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skylink |
E469405
|
entity |
| Predicate | averageHeadway |
P22511
|
FINISHED |
| Object | approximately 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: approximately 2 minutes | Statement: [Skylink, averageHeadway, approximately 2 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: averageHeadway Context triple: [Skylink, averageHeadway, approximately 2 minutes]
-
A.
transitFrequencyApprox
Indicates an approximate rate or regularity with which a transit event or service occurs between entities.
-
B.
headway
chosen
Indicates the temporal or spatial separation maintained between moving entities, such as vehicles or trains, as they travel along the same route.
-
C.
averageRecurrenceInterval
Indicates the typical time span between successive occurrences of the same type of event.
-
D.
travelTimeTypical
Indicates the usual or expected amount of time it takes to travel between two locations under normal conditions.
-
E.
offPeakServiceFrequency_minutes
Indicates the number of minutes between successive services during off-peak periods.
- 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f16613dc8190987c2d79dc616e40 |
completed | April 20, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.