Triple
T5391192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California High-Speed Rail |
E120332
|
entity |
| Predicate | plannedTopOperatingSpeed |
P2096
|
FINISHED |
| Object | 200 mph |
—
|
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: 200 mph | Statement: [California High-Speed Rail, plannedTopOperatingSpeed, 200 mph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedTopOperatingSpeed Context triple: [California High-Speed Rail, plannedTopOperatingSpeed, 200 mph]
-
A.
maxSpeed
chosen
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
B.
elevatorTopSpeed_m_per_s
Indicates the maximum speed, in meters per second, that an elevator can travel.
-
C.
speedAchieved
Indicates that a particular speed has been reached or attained by an entity during an event or action.
-
D.
recommendedSpeed
Indicates the speed that is advised or suggested as appropriate under given conditions, rather than required or actual speed.
-
E.
hasVariableSpeedLimits
Indicates that the subject is associated with speed limits that can change depending on conditions, time, or location.
- 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_69bd46354c648190a38b26f107010a96 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd87185f788190bd5244a1f7dbb5c8 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:04 p.m.