Triple
T8152853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isadora Duncan (cenotaph) |
E190370
|
entity |
| Predicate | isGraveOf |
P71625
|
FINISHED |
| Object | none (symbolic only) |
—
|
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: none (symbolic only) | Statement: [Isadora Duncan (cenotaph), isGraveOf, none (symbolic only)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGraveOf Context triple: [Isadora Duncan (cenotaph), isGraveOf, none (symbolic only)]
-
A.
isCemeteryFor
Indicates that one entity serves as the burial ground designated for another entity, such as a community, group, or location.
-
B.
hasMassGraveOf
Indicates that a location or site contains a mass grave in which the referenced individuals or remains are buried.
-
C.
formerGraveOf
Indicates that a location once served as the grave of an entity, but no longer does (e.g., the remains have been moved or the grave has been removed).
-
D.
hasGraveOccupant
chosen
Indicates that a grave is occupied by a specific person or entity.
-
E.
hasTypeOfGrave
Indicates that an entity is associated with a specific kind or category of grave.
- 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_69ca82be7ba8819087de0147e9292c83 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb44d4494c8190aad2ee302e90670f |
completed | March 31, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69cb36a0847c8190af9038aef78319b3 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:37 p.m.