Triple
T3276399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G5 Sahel |
E68767
|
entity |
| Predicate | hasTypeOfForce |
P1062
|
FINISHED |
| Object | multinational joint 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: multinational joint force | Statement: [G5 Sahel, hasTypeOfForce, multinational joint force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfForce Context triple: [G5 Sahel, hasTypeOfForce, multinational joint force]
-
A.
hasForceCarrier
Indicates that a fundamental interaction or force is mediated or carried by a specific particle or field.
-
B.
forceType
chosen
Indicates the specific kind or category of force involved in an interaction or event (e.g., physical, legal, military, or other defined force classifications).
-
C.
hasOpposingForceType
Indicates that one force is characterized as being of a type that opposes or counteracts another force.
-
D.
describesForce
Indicates that one entity characterizes, explains, or specifies the nature or magnitude of a force acting on another entity or system.
-
E.
hasMotivePowerType
Indicates that an entity (such as a vehicle or machine) operates using a specified type of motive power (e.g., electric, diesel, steam).
- 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_69ad859b54f881909bf530d549caf2fd |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0128f08819084644f3c8fda2596 |
completed | March 8, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69ada420167c81909b6e2702db296d9e |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.