Triple
T3305805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edo |
E69445
|
entity |
| Predicate | startOfEdoPeriod |
P47933
|
FINISHED |
| Object | 1603 |
—
|
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: 1603 | Statement: [Edo, startOfEdoPeriod, 1603]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfEdoPeriod Context triple: [Edo, startOfEdoPeriod, 1603]
-
A.
eraStartHeiseiYear
Indicates the calendar year in which the Heisei era begins for a given context or system of dating.
-
B.
startOfBurjiPeriod
Indicates that one event or time point marks the beginning of the Burji period in a given temporal framework.
-
C.
hasJapaneseEraDeathYear
Indicates that an entity’s year of death is specified according to the Japanese era (nengō) calendar system.
-
D.
typicalStartPeriod
Indicates the usual or standard time period during which something begins or is initiated.
-
E.
historicalEraUsheredIn
Indicates the historical era or period that was initiated or brought about as a result of a particular event, action, or entity.
- 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_69ad859f218081909458d2cebbf57565 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0c9470881908c36c1984fdbb67b |
completed | March 8, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69ada42625308190be257f16a623a410 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada526764881908e4bd52938d5374d |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:11 p.m.