Triple
T1386388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollodorus of Athens |
E29854
|
entity |
| Predicate | deathPlace_uncertain |
P28174
|
FINISHED |
| Object | likely Athens or another Greek city |
—
|
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: likely Athens or another Greek city | Statement: [Apollodorus of Athens, deathPlace_uncertain, likely Athens or another Greek city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathPlace_uncertain Context triple: [Apollodorus of Athens, deathPlace_uncertain, likely Athens or another Greek city]
-
A.
placeOfDeath
Indicates the location where an entity (typically a person or animal) died.
-
B.
deathDescribedIn
Indicates that a person's death is documented, narrated, or otherwise detailed within a particular source or description.
-
C.
burialPlace
Indicates the location where a person or entity is buried.
-
D.
diedShortlyBefore
Indicates that one entity’s death occurred a brief time before another specified event or entity’s death.
-
E.
deathStatus
Indicates whether an entity is alive, dead, or in another specified state related to mortality.
- 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_69a498dc92f8819094a1108f8ac90f43 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c33b6e108190b6b2bca4ddd97b6c |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4beffcf808190ab4cd0271257ce63 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c2f16ae081908c92792253f3eb4b |
completed | March 1, 2026, 10:51 p.m. |
Created at: March 1, 2026, 7:59 p.m.