Triple
T26201795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Islamic Republic of Afghanistan |
E655246
|
entity |
| Predicate | NATOMissionOnTerritory |
P73456
|
FINISHED |
| Object | Resolute Support Mission |
—
|
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: Resolute Support Mission | Statement: [Islamic Republic of Afghanistan, NATOMissionOnTerritory, Resolute Support Mission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NATOMissionOnTerritory Context triple: [Islamic Republic of Afghanistan, NATOMissionOnTerritory, Resolute Support Mission]
-
A.
missionTo
chosen
Indicates that one entity is assigned, directed, or sent to carry out a specific mission involving another entity or location.
-
B.
countryOfMission
Indicates that an entity (such as a mission, project, or operation) is associated with or takes place in a particular country.
-
C.
UNMission
Indicates that an entity is a United Nations peacekeeping or political mission operating in a specific area or context.
-
D.
placeOfMission
Indicates the location where a mission, assignment, or task is carried out or based.
-
E.
missionName
Indicates the designated title or label assigned to a specific mission or operation.
- 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60cdba6248190b34176bc568e7697 |
completed | May 2, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 8:48 p.m.