Triple
T783699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Special Operations Command |
E16554
|
entity |
| Predicate | hasPrimaryTask |
P2166
|
FINISHED |
| Object | counterterrorism |
—
|
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: counterterrorism | Statement: [United States Special Operations Command, hasPrimaryTask, counterterrorism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryTask Context triple: [United States Special Operations Command, hasPrimaryTask, counterterrorism]
-
A.
hasPrimaryFunction
Indicates that one entity serves as the main or principal function or role of another entity.
-
B.
primaryTask
chosen
Indicates that an entity has a main or most important task, role, or function it is responsible for above all others.
-
C.
hasPrimaryPool
Indicates that an entity is associated with or designated to use a particular pool as its main or default pool.
-
D.
hasTaskGroup
Indicates that an entity is associated with, or belongs to, a specific task group that organizes or groups related tasks.
-
E.
hasPrimarySee
Indicates that one entity is designated as the main or preferred "see" reference or cross-reference for 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_69a4936ad1fc81908f190208059ccf78 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a769dc6481908f12e872f997acf3 |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a50db97c8190a1c55673f4a357b4 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.