Triple
T9224275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 73rd Special Operations Squadron |
E221639
|
entity |
| Predicate | conflictTypeSupported |
P55719
|
FINISHED |
| Object | special operations warfare |
—
|
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: special operations warfare | Statement: [73rd Special Operations Squadron, conflictTypeSupported, special operations warfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictTypeSupported Context triple: [73rd Special Operations Squadron, conflictTypeSupported, special operations warfare]
-
A.
conflictType
Indicates the specific kind or category of conflict that characterizes the relationship or interaction between entities.
-
B.
conflictTypeManaged
Indicates that a conflict has been addressed or handled through some form of management or resolution process.
-
C.
featuresConflictType
Indicates that there is a specific type or category of conflict between the features or characteristics of the related entities.
-
D.
usedInConflictType
chosen
Indicates that something (such as a resource, method, or capability) is employed or applied within a specific type or category of conflict.
-
E.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
- 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_69ca83ec8db08190a9110df8232885d2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccda9c71c4819089dcc3689f322529 |
completed | April 1, 2026, 8:43 a.m. |
| PD | Predicate disambiguation | batch_69cc7a3daeb481908b0abde3fbc1f1f0 |
completed | April 1, 2026, 1:51 a.m. |
Created at: March 30, 2026, 7:28 p.m.