Triple
T34190884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mutsu |
E877104
|
entity |
| Predicate | serviceStartEra |
P48887
|
FINISHED |
| Object | Taisho period |
—
|
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: Taisho period | Statement: [Mutsu, serviceStartEra, Taisho period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceStartEra Context triple: [Mutsu, serviceStartEra, Taisho period]
-
A.
serviceEra
chosen
Indicates the historical period or era during which a service, role, or duty was performed.
-
B.
serviceContinuationEra
Indicates the historical or temporal period during which a service continues to operate or remain in effect.
-
C.
serviceStartContext
Indicates the circumstances or conditions under which a service begins or is initiated.
-
D.
startServiceYear
Indicates the year in which an entity began providing a particular service or started its service-related activity.
-
E.
eraStart
Indicates the point in time at which a particular era or period begins.
- 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_69f349af20a4819089ac24d28f2d8112 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: May 1, 2026, 1:55 a.m.