Triple
T37616124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fujisawa-juku |
E935924
|
entity |
| Predicate | administrativeEra |
P188412
|
FINISHED |
| Object | Tokugawa shogunate |
—
|
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: Tokugawa shogunate | Statement: [Fujisawa-juku, administrativeEra, Tokugawa shogunate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeEra Context triple: [Fujisawa-juku, administrativeEra, Tokugawa shogunate]
-
A.
dynasticEraName
Indicates the named historical period or era associated with a particular dynasty’s rule.
-
B.
governmentalEra
chosen
Indicates the historical period during which a particular government or governing authority was in power.
-
C.
historicalEraUsheredIn
Indicates the historical era or period that was initiated or brought about as a result of a particular event, action, or entity.
-
D.
constitutionalEraName
Indicates the named historical or political era associated with a particular constitution or constitutional regime.
-
E.
historicalEraOfNaming
Indicates the historical era or time period during which an entity received its name.
- 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_69f76ed16b748190ad6add183b1be688 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe7eb4b8348190bb19d35766189ed4 |
completed | May 9, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69fe7c35d2148190ab952e54feda1e76 |
completed | May 9, 2026, 12:13 a.m. |
Created at: May 3, 2026, 4:18 p.m.