Triple
T23447353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tabirqo |
E565575
|
entity |
| Predicate | possiblePosition |
P152325
|
FINISHED |
| Object | king of Kush |
—
|
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: king of Kush | Statement: [Tabirqo, possiblePosition, king of Kush]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possiblePosition Context triple: [Tabirqo, possiblePosition, king of Kush]
-
A.
possibleLocation
Indicates that an entity may be located at, or could plausibly occur in, a specified place or spatial context.
-
B.
otherPosition
Indicates that one entity occupies a different position or location relative to another entity.
-
C.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
D.
positionB
Indicates that one entity occupies or is located at a specific position relative to another entity.
-
E.
locationPosed
Indicates that an entity is positioned or situated at a specific location.
- F. None of above. chosen
Provenance (4 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_69e24584f9488190bb32730bd2ce023e |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a649f7e8819080aeb120afd57aad |
completed | April 29, 2026, 6:33 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:52 p.m.