Triple
T21258305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geoffrey III of Anjou |
E523926
|
entity |
| Predicate | causeOfLossOfPower |
P52786
|
FINISHED |
| Object | military defeats |
—
|
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: military defeats | Statement: [Geoffrey III of Anjou, causeOfLossOfPower, military defeats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfLossOfPower Context triple: [Geoffrey III of Anjou, causeOfLossOfPower, military defeats]
-
A.
reasonForLossOfPower
chosen
Indicates the cause or circumstance that led to a loss of power or authority.
-
B.
lossOfPower
Indicates that an entity experiences a reduction or complete removal of its ability to exert control, influence, or operational capability.
-
C.
lostPowerThrough
Indicates that an entity ceased to have power, authority, or control as a result of another specified entity or factor.
-
D.
lostPowerIn
Indicates that an entity has experienced a loss of electrical or functional power while in or at a specified location or context.
-
E.
lostPower
Indicates that an entity has ceased to have electrical or functional power it previously possessed.
- 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_69e0b5156d7881909bd4f83676590715 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735e477d08190be17ad5384d69a80 |
completed | April 21, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:59 p.m.