Triple
T19556973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kasta Tomb |
E489338
|
entity |
| Predicate | debatedBurialOccupant |
P65830
|
FINISHED |
| Object | high-ranking Macedonian individual |
—
|
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: high-ranking Macedonian individual | Statement: [Kasta Tomb, debatedBurialOccupant, high-ranking Macedonian individual]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: debatedBurialOccupant Context triple: [Kasta Tomb, debatedBurialOccupant, high-ranking Macedonian individual]
-
A.
hasUncertainBurialSite
Indicates that the location of an entity’s burial site is unknown, disputed, or not reliably established.
-
B.
containsSarcophagusOf
Indicates that one entity physically houses or encloses the sarcophagus belonging to another entity.
-
C.
burialDebate
Indicates a dispute or controversy over how, where, or whether a burial should take place.
-
D.
possiblyBurialOf
chosen
Indicates that one entity is a potential or uncertain burial site, grave, or interment location associated with another entity.
-
E.
originallyInterredPerson
Indicates that one entity is the person who was first buried or laid to rest at the location or in the grave represented by the other 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_69d8e8dc5d8c8190a6d7bd8864f43ca0 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63d341d708190b8ef35822f8bfe7c |
completed | April 20, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:42 p.m.