Triple
T25162845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genji |
E626487
|
entity |
| Predicate | typeOfReignMarker |
P171381
|
FINISHED |
| Object | era name |
—
|
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: era name | Statement: [Genji, typeOfReignMarker, era name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfReignMarker Context triple: [Genji, typeOfReignMarker, era name]
-
A.
reignTo
Indicates that one entity exercises ruling authority or governance over another entity or domain during a particular period.
-
B.
describesReignOf
Indicates that something (such as a text, record, or account) provides information about the period during which a particular ruler or authority was in power.
-
C.
reignCharacterizedBy
Indicates that a ruler’s period of governance is defined or distinguished by a particular quality, condition, or notable feature.
-
D.
correspondsToReignOf
Indicates that something (such as a time period, event, or record) matches or is associated with the duration of a specific ruler’s reign.
-
E.
reignStatus
Indicates the status or condition of an entity’s period of rule or governance, such as whether it is ongoing, completed, or otherwise characterized.
- 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 18, 2026, 6:31 a.m.