Triple
T16442970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ten'ō |
E399349
|
entity |
| Predicate | eraNameSystemRole |
P55932
|
FINISHED |
| Object | marker of years in imperial chronology |
—
|
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: marker of years in imperial chronology | Statement: [Ten'ō, eraNameSystemRole, marker of years in imperial chronology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraNameSystemRole Context triple: [Ten'ō, eraNameSystemRole, marker of years in imperial chronology]
-
A.
eraNameType
Indicates the type or classification of a named historical or chronological era associated with an entity.
-
B.
roleInNomenclature
chosen
Indicates the specific function or status an entity holds within a particular naming or classification system.
-
C.
unitRole
Indicates the functional role or purpose that a unit serves within a larger system or context.
-
D.
eraName
Indicates the named historical or chronological era associated with an entity or time period.
-
E.
eraOfCurrentRole
Indicates the historical or temporal era during which the entity’s current role or position is held.
- 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32cd8d2988190acb5722a15623319 |
completed | April 18, 2026, 7:03 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.