Triple
T9078637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Independence Avenue SW |
E217553
|
entity |
| Predicate | hasPublicSpaceRole |
P87086
|
FINISHED |
| Object | ceremonial route vicinity |
—
|
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: ceremonial route vicinity | Statement: [Independence Avenue SW, hasPublicSpaceRole, ceremonial route vicinity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicSpaceRole Context triple: [Independence Avenue SW, hasPublicSpaceRole, ceremonial route vicinity]
-
A.
hasPublicSpaceAlong
Indicates that a public space (such as a park, plaza, or walkway) is located adjacent to or runs alongside the referenced feature or element.
-
B.
hasPublicSpaces
Indicates that an entity includes or provides areas that are accessible and usable by the general public.
-
C.
isInPublicSpace
Indicates that an entity is located within a space that is publicly accessible or open to the general public.
-
D.
hasCommunitySpace
Indicates that an entity provides or includes a shared physical or virtual area intended for communal use, activities, or gatherings.
-
E.
usesPublicSpace
Indicates that an entity makes use of publicly accessible areas or facilities for its activities or purposes.
- 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_69ca83d6c14c8190bc056d927f00a2a2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc95c7d3688190a4c1c6a92965eae4 |
completed | April 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69cc65fa79bc81908b46f05c8bba920f |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc6a3c78388190a7436acc0e44ff55 |
completed | April 1, 2026, 12:43 a.m. |
Created at: March 30, 2026, 7:12 p.m.