Triple
T22533326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 東京都港区 |
E557098
|
entity |
| Predicate | municipalSymbol |
P10919
|
FINISHED |
| Object | 港区章 |
—
|
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: 港区章 | Statement: [東京都港区, municipalSymbol, 港区章]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: municipalSymbol Context triple: [東京都港区, municipalSymbol, 港区章]
-
A.
citySymbol
chosen
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.
municipalKey
Indicates a unique identifier that links an entity to a specific municipality within an administrative or geographic system.
-
D.
citySymbolStatus
Indicates the status or condition of a symbol associated with a city, such as whether it is official, active, or recognized.
-
E.
municipalRepresentation
Indicates that one entity serves as the official municipal-level representative or governing body for another entity within a specific locality or jurisdiction.
- 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_69e11e57483c8190b0887c4f8ff26446 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ed88cf08190ae7e5b6bf9a80372 |
completed | April 29, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69e898c864148190a3f5feec7967d49c |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:51 p.m.