Triple
T25629027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | murder of Henry Stuart, Lord Darnley |
E642522
|
entity |
| Predicate | associatedExplosion |
P107659
|
FINISHED |
| Object | house at Kirk o’ Field was blown up |
—
|
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: house at Kirk o’ Field was blown up | Statement: [murder of Henry Stuart, Lord Darnley, associatedExplosion, house at Kirk o’ Field was blown up]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedExplosion Context triple: [murder of Henry Stuart, Lord Darnley, associatedExplosion, house at Kirk o’ Field was blown up]
-
A.
explosionType
Indicates the specific kind or category of explosion associated with an event or entity.
-
B.
explosionOccurred
chosen
Indicates that an explosion event has taken place at a specific time and/or location.
-
C.
explosionEffect
Indicates that one entity causes or is associated with an explosive event that produces a sudden, forceful effect on its surroundings.
-
D.
numberOfExplosions
Indicates the count of distinct explosion events associated with an entity or situation.
-
E.
consequenceOfExplosion
Indicates that something occurs as a direct result or outcome of an explosion.
- 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_69e77e7bd4548190a0c691b8a2f27ff1 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: April 21, 2026, 5:16 p.m.