Triple
T30418876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ikeda Masanori |
E773837
|
entity |
| Predicate | domainGoverned |
P169195
|
FINISHED |
| Object | Okayama Domain |
—
|
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: Okayama Domain | Statement: [Ikeda Masanori, domainGoverned, Okayama Domain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domainGoverned Context triple: [Ikeda Masanori, domainGoverned, Okayama Domain]
-
A.
organizationTypeGoverned
Indicates that one entity governs or has authoritative control over a specific type or category of organization.
-
B.
governedDomainType
Indicates that one entity establishes rules, control, or authority over a specific type or category of domain.
-
C.
governedFor
Indicates that one entity exercised governing authority or administrative control on behalf of, or in the interest of, another entity.
-
D.
governedThrough
Indicates that one entity exercises control, authority, or administration over another entity by means of a specified intermediary mechanism, structure, or process.
-
E.
governedWith
Indicates that two or more entities share or participate together in the act or process of governing.
- F. None of above. chosen
Provenance (4 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6864cd7548190b3e12ef2fe253ad8 |
completed | May 2, 2026, 11:18 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f679496c188190ba585792f987a1f4 |
completed | May 2, 2026, 10:23 p.m. |
Created at: April 29, 2026, 8:05 p.m.