Triple
T28684235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lieutenant General Walter C. Short |
E726086
|
entity |
| Predicate | earlierConflict |
P4335
|
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: [Lieutenant General Walter C. Short, earlierConflict, World War I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlierConflict Context triple: [Lieutenant General Walter C. Short, earlierConflict, World War I]
-
A.
previousConflict
chosen
Indicates that a conflict or dispute occurred between the entities at some earlier time prior to the current context.
-
B.
existedDuringConflict
Indicates that an entity was present or active for some or all of the duration of a specified conflict.
-
C.
ledToConflict
Indicates that one event, action, or condition caused or significantly contributed to the emergence or escalation of a conflict between parties.
-
D.
recurringConflictWith
Indicates a relationship in which two entities experience conflicts or disputes that occur repeatedly over time.
-
E.
reportedConflict
Indicates that one party has formally reported the existence of a conflict involving another party or situation.
- 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_69f01d867608819086bc3e6b4f9de866 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 28, 2026, 5:11 a.m.