Triple
T19495893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skyway automated people mover |
E487767
|
entity |
| Predicate | peakServiceRole |
P136133
|
FINISHED |
| Object | downtown distributor |
—
|
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: downtown distributor | Statement: [Skyway automated people mover, peakServiceRole, downtown distributor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakServiceRole Context triple: [Skyway automated people mover, peakServiceRole, downtown distributor]
-
A.
peakService
Indicates that the service is operating during its highest-demand or peak usage period.
-
B.
peakServiceOnly
Indicates that the service operates only during peak periods and is not available at off-peak times.
-
C.
peakRole
Indicates the role or position an entity holds at the highest or most prominent point of its activity, status, or performance.
-
D.
peakServicePeriod
Indicates the time interval during which a service experiences its highest or most intensive level of use or operation.
-
E.
peakStatus
Indicates the condition or phase of something at its highest or most intense point in its progression or lifecycle.
- 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_69d8e8d9d1c88190b01cd78b8be49384 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6349182ec81908dd301f802530eec |
completed | April 20, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7bd25881908caa04eaef1f6718 |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004d3a708190a1c13c8f644f3926 |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:40 p.m.