Triple
T23476373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | royal necropolis of Meroë |
E570273
|
entity |
| Predicate | buriedIndividuals |
P25054
|
FINISHED |
| Object | Kushite kings |
—
|
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: Kushite kings | Statement: [royal necropolis of Meroë, buriedIndividuals, Kushite kings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buriedIndividuals Context triple: [royal necropolis of Meroë, buriedIndividuals, Kushite kings]
-
A.
alsoBurials
Indicates that the subject location or record includes additional burial sites or burial events beyond the primary one referenced.
-
B.
numberOfBurials
Indicates the total count of burial events associated with a given entity.
-
C.
burials
chosen
Indicates that one entity is interred or laid to rest in a grave or burial site associated with another entity.
-
D.
buriedNear
Indicates that one entity is interred or buried in close physical proximity to another entity.
-
E.
hasBurialsFrom
Indicates that a location or site contains burials originating from a specified time period, culture, or source.
- 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_69e245af8a88819084f2704f6d265a92 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a74cf57081909d2b90a806d68c08 |
completed | April 29, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:01 p.m.