Triple
T15218837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aegae |
E363708
|
entity |
| Predicate | hasRoyalTomb |
P24059
|
FINISHED |
| Object | tomb attributed to Philip II of Macedon |
—
|
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: tomb attributed to Philip II of Macedon | Statement: [Aegae, hasRoyalTomb, tomb attributed to Philip II of Macedon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoyalTomb Context triple: [Aegae, hasRoyalTomb, tomb attributed to Philip II of Macedon]
-
A.
royalNecropolis
chosen
Indicates a burial place or cemetery specifically designated for royalty or members of a royal family.
-
B.
hasMausoleum
Indicates that one entity possesses, contains, or is associated with a mausoleum dedicated to another entity.
-
C.
hasTombs
Indicates that one entity possesses, contains, or is the location of one or more tombs associated with another entity.
-
D.
hasTombDesignation
Indicates that an entity has been assigned a specific formal designation or identifier for its tomb.
-
E.
hasBurialVault
Indicates that an entity possesses or is associated with a specific burial vault used for interment or storage of remains.
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007709d3881908384f0fe1e0218d0 |
completed | April 15, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69deca8479188190b2e5d3bc708d7d07 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:11 a.m.