Triple
T35091458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meitoku |
E1012734
|
entity |
| Predicate | historicalEraCategory |
P9609
|
FINISHED |
| Object | 14th-century Japanese era |
—
|
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: 14th-century Japanese era | Statement: [Meitoku, historicalEraCategory, 14th-century Japanese era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalEraCategory Context triple: [Meitoku, historicalEraCategory, 14th-century Japanese era]
-
A.
historical era
Indicates the broad historical period or epoch during which an entity, event, or phenomenon took place or is associated.
-
B.
historicalEraOfNaming
Indicates the historical era or time period during which an entity received its name.
-
C.
historicalCategory
chosen
Indicates that an entity is classified within a particular historical grouping, period, or type based on its time-related characteristics or context.
-
D.
historicalEraOfRise
Indicates the historical era or period during which an entity first rose to prominence, influence, or significance.
-
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.
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_69f76dd432ec8190969bc32acfc152b1 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a00a094c44c81908e4501151688a635 |
completed | May 10, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_6a009fcdfd848190841deaad9667d347 |
completed | May 10, 2026, 3:10 p.m. |
Created at: May 3, 2026, 4:01 p.m.