Triple
T6099683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Police Commandos |
E135961
|
entity |
| Predicate | engagementStyle |
P3663
|
FINISHED |
| Object | direct action operations |
—
|
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: direct action operations | Statement: [Special Police Commandos, engagementStyle, direct action operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engagementStyle Context triple: [Special Police Commandos, engagementStyle, direct action operations]
-
A.
engagementType
chosen
Indicates the specific kind or category of engagement or interaction that occurs between the related entities.
-
B.
engagementTo
Indicates a formal promise or commitment between two entities to enter into a future partnership or binding relationship.
-
C.
engagementLevel
Indicates the degree or intensity of involvement, interest, or participation one entity has in relation to another entity, activity, or context.
-
D.
engagementPhase
Indicates the specific stage or phase an ongoing interaction, project, or relationship is currently in within its overall lifecycle.
-
E.
engagementCapability
Indicates the ability or capacity of one entity to initiate, conduct, or sustain an interaction or engagement with 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_69c0087cd3c48190b459848c72d84eb1 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05b3970808190ba90f5e4235db9f2 |
completed | March 22, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c049f5ac988190b62ba565153aaa35 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:13 p.m.