Triple
T31013244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jarabulus |
E790260
|
entity |
| Predicate | wasCapturedInOperation |
P72293
|
FINISHED |
| Object | Operation Euphrates Shield |
—
|
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: Operation Euphrates Shield | Statement: [Jarabulus, wasCapturedInOperation, Operation Euphrates Shield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasCapturedInOperation Context triple: [Jarabulus, wasCapturedInOperation, Operation Euphrates Shield]
-
A.
capturedInWar
Indicates that one entity was taken prisoner or seized by another entity as a result of armed conflict or wartime actions.
-
B.
SovietOperation
Indicates that an operation, mission, or organized activity is conducted by, on behalf of, or under the authority of the Soviet Union or its institutions.
-
C.
alliedOperation
Indicates that two or more entities are cooperating as allies in a shared operation or coordinated activity.
-
D.
militaryOperationName
chosen
Indicates the specific named military operation associated with an action, event, or entity.
-
E.
wasRecapturedBy
Indicates that an entity which had previously escaped or been released was caught again by another entity.
- 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:57 p.m.