Triple
T29106936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Igo |
E736785
|
entity |
| Predicate | hasGoverningBodyInJapan |
P2820
|
FINISHED |
| Object | Nihon Ki-in |
—
|
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: Nihon Ki-in | Statement: [Igo, hasGoverningBodyInJapan, Nihon Ki-in]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGoverningBodyInJapan Context triple: [Igo, hasGoverningBodyInJapan, Nihon Ki-in]
-
A.
hasMainGoverningBody
Indicates that an entity possesses a primary official organization or authority responsible for its overall governance or decision-making.
-
B.
governingBodyCountry
Indicates the country within whose jurisdiction or authority a governing body operates or to which it officially belongs.
-
C.
areGovernedBy
Indicates that one or more entities are under the authority, control, or administration of a governing body or ruler.
-
D.
hasGovernmentBody
chosen
Indicates that one entity serves as the official governing or administrative body responsible for overseeing or managing another entity.
-
E.
countryGoverningBody
Indicates that a particular governing body holds official authority over and administers a specific country.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 28, 2026, 11:16 a.m.