Triple
T27421230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lasta |
E693048
|
entity |
| Predicate | predecessorPolityContext |
P14662
|
FINISHED |
| Object | Aksumite Empire |
—
|
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: Aksumite Empire | Statement: [Lasta, predecessorPolityContext, Aksumite Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorPolityContext Context triple: [Lasta, predecessorPolityContext, Aksumite Empire]
-
A.
predecessorDynasticSituation
Indicates that one dynastic situation directly precedes another in a historical or genealogical sequence.
-
B.
historicalEntityPredecessor
chosen
Indicates that one historical entity existed or held a role before another, serving as its predecessor in time or sequence.
-
C.
predecessorCulture
Indicates that one culture historically preceded and contributed to the development of another culture.
-
D.
predecessorTerritory
Indicates that one territory previously existed in place of, or was succeeded by, another territory in a historical or political sequence.
-
E.
predecessorFaction
Indicates that one faction historically preceded and was replaced or succeeded by another faction.
- 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_69ef5208617081908f731d312e0fd1bc |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 27, 2026, 12:36 p.m.