Triple
T34515278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kita-ku, Saitama |
E886133
|
entity |
| Predicate | belongsToPrefecturalCapital |
P103943
|
FINISHED |
| Object | Saitama City |
—
|
NE NERFINISHED |
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: Saitama City | Statement: [Kita-ku, Saitama, belongsToPrefecturalCapital, Saitama City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToPrefecturalCapital Context triple: [Kita-ku, Saitama, belongsToPrefecturalCapital, Saitama City]
-
A.
belongsToPrefecturalCapitalArea
Indicates that a given place is part of, or administratively associated with, the surrounding area of a prefectural capital.
-
B.
isInPrefecturalCapital
chosen
Indicates that one entity is located within the administrative boundaries of a prefectural capital city.
-
C.
isPrefecturalCityOf
Indicates that a city holds the administrative status of a prefecture-level city within a given region or country.
-
D.
hasPrefecturalCapitalFunction
Indicates that an entity serves as the administrative capital or main governmental center of a prefecture.
-
E.
governingPrefecturalCapital
Indicates that one entity serves as the administrative capital governing a particular prefecture.
- 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_69f349ccc290819089d8e82698e53cb6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff519b65f081909902ba83b775ef85 |
completed | May 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69ff506fccdc8190bd93269589040aed |
completed | May 9, 2026, 3:19 p.m. |
Created at: May 1, 2026, 2:01 a.m.