Triple
T71387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunset Boulevard |
E1428
|
entity |
| Predicate | terminusEast |
P3569
|
FINISHED |
| Object | near Union Station in Downtown Los Angeles |
—
|
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: near Union Station in Downtown Los Angeles | Statement: [Sunset Boulevard, terminusEast, near Union Station in Downtown Los Angeles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusEast Context triple: [Sunset Boulevard, terminusEast, near Union Station in Downtown Los Angeles]
-
A.
terminusNorth
Indicates that one entity serves as the northern endpoint or final stop of another entity, such as a route, line, or path.
-
B.
terminusCity
Indicates that a transportation route or service ends or has its final stop in a particular city.
-
C.
terminus
Indicates that one entity serves as the final endpoint or stopping place for another entity’s movement, route, or process.
-
D.
endPoint
Indicates the terminal location, limit, or final state reached by an object, process, or path in a given relationship or action.
-
E.
distanceFromTerminus
Indicates the measured distance of an entity from a defined endpoint or terminus along a route, path, or sequence.
- 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_69a24c06b3bc8190aa4ac89026115efc |
completed | Feb. 28, 2026, 1:59 a.m. |
| NER | Named-entity recognition | batch_69a24f6997c081908b202f937eb2b14f |
completed | Feb. 28, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69a24eab7f408190a8275cb82474f575 |
completed | Feb. 28, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69a24f65170c8190bc541c8351456a4d |
completed | Feb. 28, 2026, 2:13 a.m. |
Created at: Feb. 28, 2026, 2:03 a.m.