Triple
T14997387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saga Domain |
E373992
|
entity |
| Predicate | kokudaka |
P116276
|
FINISHED |
| Object | 357,000 koku |
—
|
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: 357,000 koku | Statement: [Saga Domain, kokudaka, 357,000 koku]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kokudaka Context triple: [Saga Domain, kokudaka, 357,000 koku]
-
A.
aka
Indicates that one entity is also known by an alternative name or alias that refers to the same thing.
-
B.
kāṇḍa
Indicates a part–whole relationship where something is a section, chapter, or subdivision of a larger structured whole.
-
C.
ichinomiya
Indicates a relationship where a location or institution holds the status of "Ichinomiya," the primary or highest-ranking Shinto shrine of a historical province.
-
D.
kunya
Indicates the honorific or respectful name by which a person is addressed or referred to, typically reflecting esteem, modesty, or social standing.
-
E.
SakaeIs
Indicates that one entity is identified as or classified as "Sakae" in relation to another entity or context.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded718e4288190b5e144f82299a194 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a88d588190996afa8e5b32b552 |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:54 a.m.