Triple
T22983145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Formosa Resolution |
E571524
|
entity |
| Predicate | limitedToDefensiveUseOfForce |
P44969
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Formosa Resolution, limitedToDefensiveUseOfForce, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limitedToDefensiveUseOfForce Context triple: [Formosa Resolution, limitedToDefensiveUseOfForce, Yes]
-
A.
authorizedUseOfForce
Indicates that an entity has been granted legitimate permission to apply physical force under specified conditions or authority.
-
B.
defensiveUse
Indicates that an entity uses something primarily for protection or defense against threats or attacks.
-
C.
militaryForceUsed
Indicates that one entity employs or applies military power or armed force against, within, or in relation to another entity or situation.
-
D.
hasDefensivePurpose
Indicates that something exists or is designed with the primary goal of protection, defense, or safeguarding against threats or harm.
-
E.
typeOfUseOfForce
chosen
Indicates the specific manner or category of force applied in an interaction or incident.
- 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_69e245b3c50481908bb3741ec9f40862 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1829775e881909c5d6d35d3fd57f7 |
completed | April 29, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:49 p.m.