Triple
T4316517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California station (Green Line) |
E96405
|
entity |
| Predicate | platformElevation |
P21978
|
FINISHED |
| Object | above street level |
—
|
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: above street level | Statement: [California station (Green Line), platformElevation, above street level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: platformElevation Context triple: [California station (Green Line), platformElevation, above street level]
-
A.
elevationBy
Indicates a relationship where one entity raises, increases, or enhances the level, status, or intensity of another entity.
-
B.
elevationFrom
Indicates a vertical distance relationship where one entity’s height or altitude is measured relative to another reference entity.
-
C.
elevation
Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
-
D.
elevationApproxMeters
Indicates the approximate elevation of an entity above sea level, measured in meters.
-
E.
elevationContext
chosen
Indicates the contextual relationship between an entity and its elevation or vertical position relative to a reference point or environment.
- 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_69b345422aac81909ddbadae437d122e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b350f60dfc819098202b7eb3bbf402 |
completed | March 12, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69b34f4a07b08190a06ada0d9cbb14fb |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:12 p.m.