Triple
T28480711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISAF in Afghanistan |
E720681
|
entity |
| Predicate | participatingStates |
P87469
|
FINISHED |
| Object | United States |
—
|
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: United States | Statement: [ISAF in Afghanistan, participatingStates, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participatingStates Context triple: [ISAF in Afghanistan, participatingStates, United States]
-
A.
participatingState
chosen
Indicates that a state is taking part in, or is formally involved as a participant in, a specified event, process, or arrangement.
-
B.
nonParticipatingStates
Indicates that certain states are not taking part in a specified activity, agreement, or process.
-
C.
primaryStates
Indicates that certain states or conditions are the main or most fundamental ones within a given context or system.
-
D.
states
Indicates that an entity formally declares, expresses, or asserts a fact, opinion, or condition about another entity or situation.
-
E.
authorizedMemberStates
Indicates that certain member states have been granted official permission or authority to perform a specified action or exercise particular rights within a defined context.
- 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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 28, 2026, 2:55 a.m.