Triple
T27930066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Chūai |
E707954
|
entity |
| Predicate | traditionalReign |
P65487
|
FINISHED |
| Object | early 2nd century (legendary) |
—
|
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: early 2nd century (legendary) | Statement: [Emperor Chūai, traditionalReign, early 2nd century (legendary)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalReign Context triple: [Emperor Chūai, traditionalReign, early 2nd century (legendary)]
-
A.
traditionalMonarchy
Indicates a system where a monarchy operates according to long-established customs, hereditary succession, and historical institutions rather than modern or codified reforms.
-
B.
reignIs
Indicates that one entity holds ruling authority or sovereignty over another for a specified period.
-
C.
reignTo
Indicates that one entity exercises ruling authority or governance over another entity or domain during a particular period.
-
D.
traditionalDynasty
Indicates a relationship where a dynasty is recognized as traditional, typically long-established and rooted in customary or historical authority.
-
E.
traditionalRuler
chosen
Indicates that one entity holds a customary or hereditary leadership role or authority over another entity or community.
- 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: April 27, 2026, 7:02 p.m.