Triple
T12157768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 16th Street NW |
E289620
|
entity |
| Predicate | isCeremonialRoute |
P33979
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [16th Street NW, isCeremonialRoute, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCeremonialRoute Context triple: [16th Street NW, isCeremonialRoute, true]
-
A.
isCeremonial
Indicates that something is associated with, intended for, or used in a formal ceremony or ritual rather than for ordinary or practical purposes.
-
B.
ceremonialRoute
chosen
Indicates a route that is specifically used or designated for ceremonial, ritual, or formal processional purposes.
-
C.
isCeremoniallyDistinctFrom
Indicates that two entities are formally separated or differentiated from each other within a ritual, ceremonial, or symbolic context.
-
D.
openedAsCeremonialRoute
Indicates that a route was inaugurated or made accessible specifically for use in ceremonial or formal events.
-
E.
ceremonialStatus
Indicates the formal or symbolic standing an entity holds within a ritual, tradition, or official ceremony.
- 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_69d6ab4c6710819097a9d228382dde43 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915d7109481908bf5fe512bba3c89 |
completed | April 10, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69d9150c18148190bf8152189c0e5fca |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:50 p.m.