Triple
T20250021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roger d'Amory |
E498525
|
entity |
| Predicate | wasCaptured |
P45720
|
FINISHED |
| Object | after defeat in Despenser War |
—
|
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: after defeat in Despenser War | Statement: [Roger d'Amory, wasCaptured, after defeat in Despenser War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasCaptured Context triple: [Roger d'Amory, wasCaptured, after defeat in Despenser War]
-
A.
killedOrCaptured
Indicates that one entity has either killed or taken another entity into custody or control.
-
B.
wasRecapturedBy
Indicates that an entity which had previously escaped or been released was caught again by another entity.
-
C.
capturedOff
Indicates that one entity has taken another entity away or into custody, removing it from its original location or control.
-
D.
capturedBy
Indicates that one entity has been seized, taken into control, or otherwise apprehended by another entity.
-
E.
capturedInWar
chosen
Indicates that one entity was taken prisoner or seized by another entity as a result of armed conflict or wartime actions.
- 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_69da6274c58c81909c646eabed6f4f30 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e673a79a208190a5a7c0f6515bc393 |
completed | April 20, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e55b1b23f88190bdcbe2f81dd226dd |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:41 p.m.