Triple
T7003797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Brétigny |
E162399
|
entity |
| Predicate | laterUnderminedBy |
P4938
|
FINISHED |
| Object | renewal of the Hundred Years' 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: renewal of the Hundred Years' War | Statement: [Treaty of Brétigny, laterUnderminedBy, renewal of the Hundred Years' War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterUnderminedBy Context triple: [Treaty of Brétigny, laterUnderminedBy, renewal of the Hundred Years' War]
-
A.
undermined
chosen
Indicates that one entity has weakened, subverted, or reduced the effectiveness, authority, or stability of another entity or its position.
-
B.
declineBeganUnder
Indicates that a period of decline started during the tenure, rule, or administration of a specified entity.
-
C.
laterUnderRuleOf
Indicates that one entity came to be governed or ruled by another entity at a later point in time.
-
D.
minedBy
Indicates that a resource, material, or location is extracted or obtained through mining activities performed by a specified agent or entity.
-
E.
under
Indicates that one entity is positioned below or beneath another entity, often implying vertical alignment or coverage.
- 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_69c6885928148190ae31909fbb5e9849 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc12af788190b3d06ffc46568410 |
completed | March 27, 2026, 7:35 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c67c94819084fdcf0398606027 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:33 p.m.