Triple
T23431368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 6th Street NW |
E563340
|
entity |
| Predicate | belongsToQuadrantSystem |
P152250
|
FINISHED |
| Object | NW quadrant designation |
—
|
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: NW quadrant designation | Statement: [6th Street NW, belongsToQuadrantSystem, NW quadrant designation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToQuadrantSystem Context triple: [6th Street NW, belongsToQuadrantSystem, NW quadrant designation]
-
A.
inGalacticQuadrant
Indicates that one entity (typically a location or object) is situated within a specified galactic quadrant in space.
-
B.
hasQuadrantRole
Indicates that an entity holds a specific functional or positional role within a defined quadrant of a larger structure or system.
-
C.
isInGalacticSystem
Indicates that one astronomical object is located within or belongs to a particular galactic system.
-
D.
hasQuadrants
Indicates that something is divided into four distinct sections or regions, typically arranged as quadrants.
-
E.
inGalacticHemisphere
Indicates that one entity is located within the same specified galactic hemisphere as another entity or reference frame.
- 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_69e24553980c8190bb66a2ae0bdab125 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a5d8130881909e4f3455afef1804 |
completed | April 29, 2026, 6:31 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:49 p.m.