Triple
T17047395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William d'Aubigny |
E413604
|
entity |
| Predicate | legalStatusDuringConflict |
P47615
|
FINISHED |
| Object | rebel subject of the king |
—
|
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 subject of the king | Statement: [William d'Aubigny, legalStatusDuringConflict, rebel subject of the king]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusDuringConflict Context triple: [William d'Aubigny, legalStatusDuringConflict, rebel subject of the king]
-
A.
legalStatusAfterWar
Indicates the legal condition or classification assigned to an entity as a consequence of, or following the conclusion of, a war or armed conflict.
-
B.
conflictRelatedStatus
chosen
Indicates a status or condition that is directly associated with, affected by, or resulting from a conflict.
-
C.
beganDuringConflict
Indicates that the action or relationship started while a specified conflict was ongoing.
-
D.
builtDuringConflict
Indicates that the construction of one entity occurred while a specified conflict or war was taking place.
-
E.
warStatus
Indicates the state or condition of conflict or war that exists between entities at a given time.
- 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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3da9f799c8190a683ae38cd990643 |
completed | April 18, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69e35d60a588819084f53ef9f8b2e7c0 |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:34 a.m.