Triple
T33136260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilhelmshaven Imperial Shipyard |
E848013
|
entity |
| Predicate | conflictInvolvedPeriod |
P28865
|
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: [Wilhelmshaven Imperial Shipyard, conflictInvolvedPeriod, World War I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictInvolvedPeriod Context triple: [Wilhelmshaven Imperial Shipyard, conflictInvolvedPeriod, World War I]
-
A.
conflictPeriod
chosen
Indicates the time span during which a particular conflict or dispute is occurring or in effect between the related entities.
-
B.
conflictBeganInYear
Indicates that the specified conflict started or first broke out in the given calendar year.
-
C.
conflictEra
Indicates that two entities are associated with the same historical period or era of conflict.
-
D.
conflictsInvolvedIn
Indicates that an entity participates as a party or actor in one or more conflicts.
-
E.
hasMonthOfConflict
Indicates that a conflict is associated with, occurs in, or is characterized by a specific calendar month.
- 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_69f3495961d88190b16ea542c2c5f825 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:27 a.m.