Triple
T31858766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byzantine tagmata |
E813265
|
entity |
| Predicate | significantReign |
P111356
|
FINISHED |
| Object | Constantine V |
—
|
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: Constantine V | Statement: [Byzantine tagmata, significantReign, Constantine V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantReign Context triple: [Byzantine tagmata, significantReign, Constantine V]
-
A.
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.
-
B.
stillReigning
Indicates that a ruler or leader continues to hold their position of authority at the referenced point in time.
-
C.
reignAfter
Indicates that one entity begins its reign or rule following the conclusion of another entity's reign.
-
D.
hasNotableReign
chosen
Indicates that an entity’s period of rule or governance is recognized as particularly significant or noteworthy.
-
E.
reignCharacterizedBy
Indicates that a ruler’s period of governance is defined or distinguished by a particular quality, condition, or notable feature.
- 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_69f348ebf32881908d9439646933dc76 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 30, 2026, 11:52 p.m.