Triple
T9576576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Test Track pavilion |
E231059
|
entity |
| Predicate | usesSingleRiderLine |
P30894
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Test Track pavilion, usesSingleRiderLine, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSingleRiderLine Context triple: [Test Track pavilion, usesSingleRiderLine, yes]
-
A.
hasSingleRiderLine
chosen
Indicates that a ride or attraction offers a dedicated line for solo riders, separate from the regular queue.
-
B.
isOnlyRailSystemIn
Indicates that the subject rail system is the sole rail system operating within the specified area or jurisdiction.
-
C.
hasShuttleLine
Indicates that there is a shuttle service or route operating between the related entities.
-
D.
lineServed
Indicates that a particular transportation line (such as a bus, train, or metro line) provides service to or is operated at a given stop, station, or route segment.
-
E.
isOnlyRailStationServing
Indicates that one rail station is the sole station providing service to a particular area, route, or entity, with no alternative rail stations serving it.
- 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_69ca848091c48190bc313d6620d09555 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99ac17a48190bb8448394f22b1e9 |
completed | April 1, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69ccd59fd7408190b36831902e3f37f7 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:05 p.m.