Triple
T17665387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Takatsu-ku |
E440363
|
entity |
| Predicate | municipalSymbolType |
P10919
|
FINISHED |
| Object | ward symbol |
—
|
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: ward symbol | Statement: [Takatsu-ku, municipalSymbolType, ward symbol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: municipalSymbolType Context triple: [Takatsu-ku, municipalSymbolType, ward symbol]
-
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.
citySymbolStatus
Indicates the status or condition of a symbol associated with a city, such as whether it is official, active, or recognized.
-
D.
isPartOfMunicipalityType
Indicates that one administrative unit or area belongs to, or is classified under, a specific type or category of municipality.
-
E.
municipalWardType
Indicates the specific category or classification of a municipal ward within a local government or administrative structure.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46ea8accc8190beea0900b0614020 |
completed | April 19, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 9:56 a.m.