Triple
T6663632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gabriel de Montgomery |
E151539
|
entity |
| Predicate | causeOfHenryIIDeath |
P144
|
FINISHED |
| Object | jousting lance splinter through the eye |
—
|
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: jousting lance splinter through the eye | Statement: [Gabriel de Montgomery, causeOfHenryIIDeath, jousting lance splinter through the eye]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfHenryIIDeath Context triple: [Gabriel de Montgomery, causeOfHenryIIDeath, jousting lance splinter through the eye]
-
A.
reasonForDeath
Indicates the cause, circumstance, or condition that led to an entity’s death.
-
B.
causeOfDeath
chosen
Indicates the specific factor, event, or condition that directly resulted in an entity’s death.
-
C.
discoveredAsDeadBy
Indicates that one entity was found to be dead by another entity, who discovered their deceased state.
-
D.
deathCharacteristic
Indicates a characteristic, attribute, or quality specifically associated with a death event or the manner in which death occurred.
-
E.
endOfReignReason
Indicates the cause or circumstance that led to the termination of a ruler’s reign.
- 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_69c687f5fac48190a09e4838d9c6b45d |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9d53848190ac75523c157249c6 |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad071b0081909b96dd4b93414bd1 |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:02 p.m.