Triple
T31669014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Izushi |
E808216
|
entity |
| Predicate | historicalPeriodProminence |
P4928
|
FINISHED |
| Object | Edo 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: Edo period | Statement: [Izushi, historicalPeriodProminence, Edo period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPeriodProminence Context triple: [Izushi, historicalPeriodProminence, Edo period]
-
A.
historicalPeriodOfSignificance
chosen
Indicates the time period during which an entity is considered to have had its most important or influential historical impact.
-
B.
historicalNotability
Indicates that an entity is recognized as having significant importance, influence, or prominence in history.
-
C.
historicalPeriodPraisedSince
Indicates that a particular historical period has been positively regarded or praised starting from a specific point in time and continuing thereafter.
-
D.
notablePeriodOfInterest
Indicates a time span that is particularly significant or noteworthy in relation to the subject.
-
E.
notablePopularityPeriod
Indicates the time span during which something was especially popular or widely recognized.
- 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff5803c02c81908b63067119f5e684 |
completed | May 9, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69ff576d8b308190b49a1e072a0ae661 |
completed | May 9, 2026, 3:49 p.m. |
Created at: April 30, 2026, 11 p.m.