Triple
T29679101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alwa |
E750901
|
entity |
| Predicate | predecessorInRegion |
P180319
|
FINISHED |
| Object | Kingdom of Kush |
—
|
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: Kingdom of Kush | Statement: [Alwa, predecessorInRegion, Kingdom of Kush]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorInRegion Context triple: [Alwa, predecessorInRegion, Kingdom of Kush]
-
A.
predecessorLocatedAt
Indicates that the location specified was the place where the immediately preceding version, state, or instance of an entity was situated.
-
B.
predecessorArea
Indicates that one area previously existed or was defined before another area in a sequence or versioning of areas.
-
C.
successorInRegion
Indicates that one entity directly follows or replaces another within a specified region or jurisdiction.
-
D.
predecessorAutonomousRegion
Indicates that one autonomous region previously existed in place of, or was succeeded by, another autonomous region in an administrative or historical sequence.
-
E.
predecessorInLocationOf
chosen
Indicates that one entity previously occupied or held a position in a specific location that is now occupied or held by another entity.
- 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_69f0d624d7b08190ba237d226f78d0d9 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 28, 2026, 7:09 p.m.