Triple
T37060704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 奈良県生駒市 |
E917314
|
entity |
| Predicate | ISO 3166-2:JP |
P99937
|
FINISHED |
| Object | JP-29 |
—
|
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: JP-29 | Statement: [奈良県生駒市, ISO 3166-2:JP, JP-29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISO 3166-2:JP Context triple: [奈良県生駒市, ISO 3166-2:JP, JP-29]
-
A.
regionOfJapan
Indicates that one entity is a geographic region that is part of, or located within, Japan.
-
B.
都道府県
Indicates a relationship where an entity is a Japanese prefecture or belongs to/pertains to a specific Japanese prefecture.
-
C.
hasPrefecturalCode
chosen
Indicates that an entity is associated with a specific prefectural identification code assigned by an administrative system.
-
D.
isPrefecturalCityOf
Indicates that a city holds the administrative status of a prefecture-level city within a given region or country.
-
E.
isPrefecture
Indicates that one entity functions as an administrative prefecture governing or representing the other entity.
- 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_69f76e95fa40819091e14681087ae5e4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.