Triple
T25019884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Sedeinga |
E626541
|
entity |
| Predicate | hasNecropolisFor |
P76264
|
FINISHED |
| Object | Kushite nobility |
—
|
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: Kushite nobility | Statement: [Temple of Sedeinga, hasNecropolisFor, Kushite nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNecropolisFor Context triple: [Temple of Sedeinga, hasNecropolisFor, Kushite nobility]
-
A.
belongsToNecropolis
chosen
Indicates that something is part of, contained within, or associated with a particular necropolis.
-
B.
hasTombs
Indicates that one entity possesses, contains, or is the location of one or more tombs associated with another entity.
-
C.
hasMortuaryTemple
Indicates that a person, ruler, or deity is associated with or honored by a specific mortuary temple built for their funerary or commemorative purposes.
-
D.
hasBurialMonumentType
Indicates that an entity is associated with a burial whose monument is of a specified type.
-
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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 18, 2026, 6:06 a.m.