Triple
T20250019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roger d'Amory |
E498525
|
entity |
| Predicate | roleInDespenserWar |
P139396
|
FINISHED |
| Object | rebel baron against Despensers |
—
|
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: rebel baron against Despensers | Statement: [Roger d'Amory, roleInDespenserWar, rebel baron against Despensers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInDespenserWar Context triple: [Roger d'Amory, roleInDespenserWar, rebel baron against Despensers]
-
A.
roleInWZRD
Indicates that an entity holds a specific role or function within the context of WZRD.
-
B.
roleInGameplay
Indicates the specific function or responsibility an entity has within the context of gameplay or game mechanics.
-
C.
roleInRepertoire
Indicates that an entity serves a specific role or function within a larger repertoire, collection, or set of items.
-
D.
roleInTimeWar
Indicates that an entity held a specific role or function during the period or events referred to as the Time War.
-
E.
roleInPurifiers
Indicates that an entity holds a specific role or function within a group, system, or organization referred to as "Purifiers."
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:41 p.m.