Triple
T30403821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jozenji-dori Avenue |
E773421
|
entity |
| Predicate | citySymbolRole |
P156924
|
FINISHED |
| Object | symbolic street of Sendai |
—
|
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: symbolic street of Sendai | Statement: [Jozenji-dori Avenue, citySymbolRole, symbolic street of Sendai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: citySymbolRole Context triple: [Jozenji-dori Avenue, citySymbolRole, symbolic street of Sendai]
-
A.
citySymbol
Indicates that one entity serves as the official symbol or emblem representing a particular city.
-
B.
cityAsSymbol
Indicates that a city functions as a symbol or emblem representing an idea, value, or broader concept in relation to another entity.
-
C.
citySymbolOf
Indicates that a particular city serves as an official symbol or emblem representing another entity, such as a region, organization, or concept.
-
D.
citySymbolStatus
Indicates the status or condition of a symbol associated with a city, such as whether it is official, active, or recognized.
-
E.
isMunicipalSymbolOf
chosen
Indicates that something serves as an official municipal symbol representing a particular city or local government.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:03 p.m.