Triple
T29338218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rapid Action Force |
E743967
|
entity |
| Predicate | usesForceDoctrine |
P4473
|
FINISHED |
| Object | minimum necessary force |
—
|
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: minimum necessary force | Statement: [Rapid Action Force, usesForceDoctrine, minimum necessary force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesForceDoctrine Context triple: [Rapid Action Force, usesForceDoctrine, minimum necessary force]
-
A.
usesDoctrine
chosen
Indicates that one entity applies, follows, or relies on a particular doctrine in its actions or reasoning.
-
B.
extendsDoctrineTo
Indicates that a doctrine, principle, or rule is applied or carried over from one context, entity, or domain to another, broadening its scope or coverage.
-
C.
containsDoctrine
Indicates that one entity includes, embodies, or incorporates the doctrine, principles, or teachings represented by another entity.
-
D.
sharesDoctrine
Indicates that two entities adhere to or promote the same doctrine, belief system, or set of principles.
-
E.
currentDoctrine
Indicates the doctrine, policy, or set of guiding principles that is presently in force or officially adopted at a given time.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 28, 2026, 1:32 p.m.