Triple
T6645046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royce Hall |
E150678
|
entity |
| Predicate | locatedAtCoordinates |
P1573
|
FINISHED |
| Object | approximately 34.072°N 118.442°W |
—
|
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: approximately 34.072°N 118.442°W | Statement: [Royce Hall, locatedAtCoordinates, approximately 34.072°N 118.442°W]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedAtCoordinates Context triple: [Royce Hall, locatedAtCoordinates, approximately 34.072°N 118.442°W]
-
A.
coordinateLocation
chosen
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
-
B.
locatedAlong
Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
-
C.
locationOnSquare
Indicates that one entity is positioned on a specific square region or cell within a larger spatial grid or board.
-
D.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
E.
locatedAtInteractionPoint
Indicates that an entity is positioned at a specific interaction point where interactions or exchanges are intended to occur.
- 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_69c687f1a3048190828b7342f7125d5c |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad04d66c8190926ffcbff372643b |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2 p.m.