Triple
T27540139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council Joint Action 2007/369/CFSP |
E695211
|
entity |
| Predicate | missionTheatre |
P687
|
FINISHED |
| Object | Afghanistan |
—
|
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: Afghanistan | Statement: [Council Joint Action 2007/369/CFSP, missionTheatre, Afghanistan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionTheatre Context triple: [Council Joint Action 2007/369/CFSP, missionTheatre, Afghanistan]
-
A.
militaryTheater
Indicates that an entity is a geographic or operational area where military operations or campaigns are conducted.
-
B.
theaterOfWar
chosen
Indicates that a specified location or region is the primary area where a particular conflict, war, or military operation takes place.
-
C.
theatreOfService
Indicates the geographic or operational area where a service, duty, or activity is performed or applicable.
-
D.
theatreOf
Indicates that an event, action, or operation takes place within or is primarily associated with a particular theatre or venue.
-
E.
intendedTheatre
Indicates a relationship where an entity is planned, designed, or meant to be performed, shown, or take place in a particular theatre.
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 1:30 p.m.