Triple
T24174163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spaanse Rijk |
E599229
|
entity |
| Predicate | belangrijkeOorlog |
P5051
|
FINISHED |
| Object | Tachtigjarige Oorlog |
—
|
NE NERFINISHED |
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: Tachtigjarige Oorlog | Statement: [Spaanse Rijk, belangrijkeOorlog, Tachtigjarige Oorlog]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belangrijkeOorlog Context triple: [Spaanse Rijk, belangrijkeOorlog, Tachtigjarige Oorlog]
-
A.
majorWar
chosen
Indicates a large-scale, intense armed conflict between major powers or involving substantial military forces and widespread impact.
-
B.
warName
Indicates the specific name or title assigned to a particular war or armed conflict.
-
C.
nomDeGuerre
Indicates that an entity uses or is known by a pseudonymous or war-related alias instead of their real name.
-
D.
thirdMajorWar
Indicates that the entities are involved in, associated with, or constitute the third major war in a given historical or contextual sequence.
-
E.
worldWar
Indicates a large-scale armed conflict involving multiple nations across different regions of the world, typically encompassing numerous battles, alliances, and theaters of war.
- 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_69e288cca05481908faeb1563711114a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:33 p.m.