Triple
T30531001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Tetrarchy |
E776998
|
entity |
| Predicate | hasPredecessorSystem |
P9736
|
FINISHED |
| Object | First Tetrarchy |
—
|
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: First Tetrarchy | Statement: [Second Tetrarchy, hasPredecessorSystem, First Tetrarchy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPredecessorSystem Context triple: [Second Tetrarchy, hasPredecessorSystem, First Tetrarchy]
-
A.
predecessorSystem
chosen
Indicates that one system existed or was in use before and was replaced or superseded by another system.
-
B.
predecessorSystemType
Indicates that one system type functioned as the predecessor or earlier version to another system type.
-
C.
hasPredecessorMP
Indicates that one member of parliament previously held the same parliamentary position or seat before another member of parliament.
-
D.
hasPrecedenceSystem
Indicates that one system is defined as having priority or a higher order of precedence over another system in determining outcomes or rules.
-
E.
hasPredecessorGeneration
Indicates that one generation directly precedes another in a temporal or genealogical sequence.
- 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_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fff328ddc0819080642334a41fcf95 |
completed | May 10, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69fff2e0971c819081aa66f4a6a34b28 |
completed | May 10, 2026, 2:52 a.m. |
Created at: April 29, 2026, 8:18 p.m.