Triple
T33066749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Street (Utah) |
E846119
|
entity |
| Predicate | isNumberingAxisFor |
P116210
|
FINISHED |
| Object | Salt Lake City street grid |
—
|
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: Salt Lake City street grid | Statement: [State Street (Utah), isNumberingAxisFor, Salt Lake City street grid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNumberingAxisFor Context triple: [State Street (Utah), isNumberingAxisFor, Salt Lake City street grid]
-
A.
isAxisDirection
Indicates that one direction is aligned with or corresponds to a principal axis (such as x, y, or z) in a given coordinate system.
-
B.
hasNumberingWithin
chosen
Indicates that one entity assigns or follows a specific numbering scheme within the scope or structure of another entity.
-
C.
hasNumberingRole
Indicates that an entity holds a specific role or responsibility related to assigning, managing, or using numbers within a given context.
-
D.
isAxisBetween
Indicates that one entity serves as a central or reference axis positioned between two other entities in a spatial or structural arrangement.
-
E.
hasAxisCount
Indicates that an entity is associated with a specified number of axes.
- 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_69f3495405b88190967af2157b43b896 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:25 a.m.