Triple
T38634223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spec Ops |
E937535
|
entity |
| Predicate | includesObjectiveType |
P99631
|
FINISHED |
| Object | hostage rescue |
—
|
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: hostage rescue | Statement: [Spec Ops, includesObjectiveType, hostage rescue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesObjectiveType Context triple: [Spec Ops, includesObjectiveType, hostage rescue]
-
A.
hasObjectiveTypes
chosen
Indicates that an entity is associated with one or more specific types or categories of objectives it aims to achieve.
-
B.
objectiveIncludes
Indicates that a broader objective encompasses or contains a specific sub-objective, component, or element as part of its scope.
-
C.
usesObjective
Indicates that an agent employs or applies a particular object, tool, or resource to carry out an action or achieve a goal.
-
D.
isObjectiveBased
Indicates that something is determined, structured, or evaluated according to predefined objectives or goals.
-
E.
includesTypeOfObject
Indicates that one entity contains or encompasses another entity that is a specific type or category of object.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.