Triple
T6193882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl Spencer |
E138461
|
entity |
| Predicate | associatedWithBurialPlace |
P196
|
FINISHED |
| Object | Althorp, island on the Round Oval lake |
—
|
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: Althorp, island on the Round Oval lake | Statement: [Earl Spencer, associatedWithBurialPlace, Althorp, island on the Round Oval lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithBurialPlace Context triple: [Earl Spencer, associatedWithBurialPlace, Althorp, island on the Round Oval lake]
-
A.
burialPlace
chosen
Indicates the location where a person or entity is buried.
-
B.
hasBurialsFrom
Indicates that a location or site contains burials originating from a specified time period, culture, or source.
-
C.
buriedWith
Indicates that one entity is interred in the same grave, tomb, or burial site as another entity.
-
D.
hasMassGraveOf
Indicates that a location or site contains a mass grave in which the referenced individuals or remains are buried.
-
E.
hasBurialsOf
Indicates that a location or site contains or includes the burial places of certain individuals or groups.
- 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_69c008ab9b3081908a11b2c744838435 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062431ae88190a1bf6ca91f3dc690 |
completed | March 22, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c055fbce1081908805fd12e242ab96 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:19 p.m.