Triple
T2161602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bir el Gubi |
E46811
|
entity |
| Predicate | conflictOutcomeContext |
P3680
|
FINISHED |
| Object | linked to Operation Crusader |
—
|
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: linked to Operation Crusader | Statement: [Bir el Gubi, conflictOutcomeContext, linked to Operation Crusader]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictOutcomeContext Context triple: [Bir el Gubi, conflictOutcomeContext, linked to Operation Crusader]
-
A.
conflictContext
chosen
Indicates the situational background or circumstances within which a conflict between entities occurs or is interpreted.
-
B.
conflictResult
Indicates the outcome or consequence that arises from a particular conflict between entities.
-
C.
conflictOfEstablishmentContext
Indicates that there is a disagreement, incompatibility, or clash within the situational or institutional context in which something is established or set up.
-
D.
conflictResolvedBy
Indicates that a conflict or dispute is settled or addressed through the actions, decisions, or intervention of a specified entity or process.
-
E.
endedConflict
Indicates that a previously ongoing conflict between entities has been brought to an end.
- 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_69a88a184cbc8190877791f6552c2484 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe89e6ac8190b4b4bc0be4fe7aa9 |
completed | March 7, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69abbd9c90408190b6b65498ca43ce26 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.