Triple
T8878021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Stuart, Lord Darnley |
E211336
|
entity |
| Predicate | bodyFoundLocation |
P66081
|
FINISHED |
| Object | garden near Kirk o’ Field, Edinburgh |
—
|
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: garden near Kirk o’ Field, Edinburgh | Statement: [Henry Stuart, Lord Darnley, bodyFoundLocation, garden near Kirk o’ Field, Edinburgh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyFoundLocation Context triple: [Henry Stuart, Lord Darnley, bodyFoundLocation, garden near Kirk o’ Field, Edinburgh]
-
A.
bodyFound
chosen
Indicates that the location or circumstance where a body was discovered has been identified or recorded.
-
B.
locatedOnBody
Indicates that one entity is physically situated on the surface or external part of another entity’s body.
-
C.
objectLocation
Indicates that one entity is located at, in, or on another entity or spatial region.
-
D.
bodyDiscoveredIncorrupt
Indicates that a body was found in an unusually preserved or undecayed state, contrary to normal expectations of decomposition.
-
E.
sourceLocatedOn
Indicates that the source entity is physically situated on the surface or area of the target 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_69ca838e78748190934d82db3104f855 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc61496870819097c55c73aca62aac |
completed | April 1, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2956788190a311c647b4da17a6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:52 p.m.