Triple
T24007092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanba Province |
E594417
|
entity |
| Predicate | duringEdoPeriod |
P154839
|
FINISHED |
| Object | dividedIntoSeveralDomains |
—
|
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: dividedIntoSeveralDomains | Statement: [Tanba Province, duringEdoPeriod, dividedIntoSeveralDomains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: duringEdoPeriod Context triple: [Tanba Province, duringEdoPeriod, dividedIntoSeveralDomains]
-
A.
roleInEdoPeriod
Indicates that an entity held a specific role, position, or function during Japan’s Edo period.
-
B.
endOfEdoPeriod
Indicates that an event, state, or condition occurs at or marks the conclusion of the Edo period.
-
C.
inJapaneseHistory
Indicates that something occurs within, belongs to, or is specifically situated in the context of Japanese history.
-
D.
startOfEdoPeriod
Indicates that something marks the beginning or initial phase of the Edo period in Japanese history.
-
E.
roleInMeijiRestoration
Indicates the specific part, function, or contribution an entity had in bringing about or shaping the Meiji Restoration.
- 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_69e288bc8f608190ac4af29f0bd1c744 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d46a6ba48190b0cce0b134dfb35f |
completed | April 29, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f17c28b684819084eea522126463f8 |
completed | April 29, 2026, 3:34 a.m. |
Created at: April 17, 2026, 9:40 p.m.