Triple
T33386918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siemens SD-460 |
E854938
|
entity |
| Predicate | serviceCity |
P3936
|
FINISHED |
| Object | St. Louis |
—
|
NE NERFINISHED |
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: St. Louis | Statement: [Siemens SD-460, serviceCity, St. Louis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceCity Context triple: [Siemens SD-460, serviceCity, St. Louis]
-
A.
servedCity
chosen
Indicates that a service, route, or facility operates in, reaches, or is available to a particular city.
-
B.
projectCity
Indicates that a project is located in, associated with, or primarily takes place within a specific city.
-
C.
stationCity
Indicates that a station is located in or associated with a particular city.
-
D.
cityIs
Indicates that one entity is a city associated with, or identified as, another entity.
-
E.
alternativeCityServed
Indicates that one city functions as an alternative service location for another city, typically in contexts like transportation or logistics.
- 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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 1, 2026, 1:35 a.m.