Triple
T7994973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Go By Train |
E186101
|
entity |
| Predicate | relationToBuilding |
P59923
|
FINISHED |
| Object | installed on top of the station tower |
—
|
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: installed on top of the station tower | Statement: [Go By Train, relationToBuilding, installed on top of the station tower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationToBuilding Context triple: [Go By Train, relationToBuilding, installed on top of the station tower]
-
A.
belongsToBuildingComplex
Indicates that one building or structure is part of, or included within, a larger building complex.
-
B.
positionRelativeToBuilding
chosen
Indicates the spatial relationship of an entity’s location with respect to a specific building (e.g., in front of, behind, adjacent to, on top of).
-
C.
relationshipBetweenHouses
Indicates a relational connection or association that exists between two or more houses.
-
D.
relationToMLS
Indicates a relationship or association that an entity has with a specific MLS (Multiple Listing Service) system or record.
-
E.
locatedInBuildingOwnedBy
Indicates that one entity is situated within a building that is owned by another entity.
- 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_69ca829c6c308190ab05b43d234c52b2 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c7547dc8190a60a06b3d61764b0 |
completed | March 31, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69cb0483d3b48190b250c7603d747bca |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:17 p.m.