Triple
T23865248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alban kings |
E592559
|
entity |
| Predicate | precedesDynasty |
P46282
|
FINISHED |
| Object | Roman kings |
—
|
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: Roman kings | Statement: [Alban kings, precedesDynasty, Roman kings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precedesDynasty Context triple: [Alban kings, precedesDynasty, Roman kings]
-
A.
earlierDynasty
chosen
Indicates that one dynasty chronologically precedes another in historical succession.
-
B.
nativeDynasty
Indicates that a dynasty is indigenous to, or originally from, the place or polity it rules or is associated with.
-
C.
historicalEntityPredecessor
Indicates that one historical entity existed or held a role before another, serving as its predecessor in time or sequence.
-
D.
reignPreceded
Indicates that one entity’s reign occurred immediately before another entity’s reign in a temporal succession.
-
E.
predecessorAsEasternRuler
Indicates that one entity previously held the position of eastern ruler before another entity assumed that same role.
- 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_69e25d22eb488190914b193aff952e83 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cae318cc8190afd0915517964494 |
completed | April 29, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:13 p.m.