Triple
T24438759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Babusch |
E616198
|
entity |
| Predicate | associatedWithConflictContext |
P3680
|
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: [Babusch, associatedWithConflictContext, World War I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithConflictContext Context triple: [Babusch, associatedWithConflictContext, World War I]
-
A.
conflictContext
chosen
Indicates the situational background or circumstances within which a conflict between entities occurs or is interpreted.
-
B.
conflictWith
Indicates that two entities are in opposition or disagreement, such that their goals, actions, or states are incompatible or interfere with each other.
-
C.
appliesToConflictWith
Indicates that one element’s scope, rules, or effects are relevant to a conflict involving another element, defining how that element is implicated in or governed by the conflict.
-
D.
associatedConflictImpact
Indicates a relationship where an entity is linked to a specific conflict and the effects or consequences that conflict has on it.
-
E.
hasRelatedConflict
Indicates that one entity is associated with another entity through a related or connected conflict, dispute, or incompatibility.
- 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_69e2d7ec44b081909ccaf1f3bbec0641 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f297891f108190a98e55c900494d30 |
completed | April 29, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:16 a.m.