Triple
T25263141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oharai-machi |
E633359
|
entity |
| Predicate | hasHistoricalPeriodStyle |
P58089
|
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: [Oharai-machi, hasHistoricalPeriodStyle, Edo period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalPeriodStyle Context triple: [Oharai-machi, hasHistoricalPeriodStyle, Edo period]
-
A.
hasHistoricRegionStyle
Indicates that an entity exhibits or is characterized by the architectural or cultural style associated with a particular historic region.
-
B.
hasHistoryPeriod
chosen
Indicates that something is associated with, belongs to, or occurs within a specific historical period or era.
-
C.
hasHistoricity
Indicates that something possesses historical existence, significance, or authenticity, rather than being purely fictional, mythical, or timeless.
-
D.
hasHistoricalCategory
Indicates that something is associated with a particular historical classification, period, or type based on its past context or significance.
-
E.
hasHistoricalSection
Indicates that something includes a dedicated part or segment that presents historical information or context.
- 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 21, 2026, 1:14 p.m.