Triple
T28133877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forth defences |
E714143
|
entity |
| Predicate | developedForConflict |
P155098
|
FINISHED |
| Object | World War I |
—
|
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: World War I | Statement: [Forth defences, developedForConflict, World War I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedForConflict Context triple: [Forth defences, developedForConflict, World War I]
-
A.
builtForConflict
Indicates that something is specifically designed or intended to function effectively in situations of conflict or confrontation.
-
B.
developedDuringConflict
chosen
Indicates that something was created, advanced, or significantly progressed while an identified conflict (such as a war, dispute, or crisis) was ongoing.
-
C.
militaryConflict
Indicates a relationship where two or more parties are engaged in organized, armed hostilities or warfare against each other.
-
D.
builtForConflictContext
Indicates that something is designed, adapted, or intended specifically to function within or address a conflict situation or contentious context.
-
E.
conflictIntroduced
Indicates that a conflict has been newly created or brought into existence between the related entities.
- 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_69efd6af156c81908f50c2cd7db0e1ef |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 27, 2026, 9:48 p.m.