Triple
T17269539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hollandia |
E419215
|
entity |
| Predicate | afterWarStatus |
P4701
|
FINISHED |
| Object | reduced military importance after World War II |
—
|
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: reduced military importance after World War II | Statement: [Hollandia, afterWarStatus, reduced military importance after World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterWarStatus Context triple: [Hollandia, afterWarStatus, reduced military importance after World War II]
-
A.
legalStatusAfterWar
chosen
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.
usedAfterWar
Indicates that an entity came into use only after a specific war or conflict had ended.
-
C.
warStatus
Indicates the state or condition of conflict or war that exists between entities at a given time.
-
D.
concludedWar
Indicates that a war or armed conflict between entities has come to an end, typically through victory, surrender, or formal agreement.
-
E.
operatorAfterWar
Indicates that one entity serves or functions as an operator after the occurrence or end of a 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42f4803b48190894b3bb9a4970602 |
completed | April 19, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:40 a.m.