Triple
T34876770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loyada school bus hostage rescue |
E1005900
|
entity |
| Predicate | usedForceBy |
P85138
|
FINISHED |
| Object | France |
—
|
NE NERFINISHED |
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: France | Statement: [Loyada school bus hostage rescue, usedForceBy, France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForceBy Context triple: [Loyada school bus hostage rescue, usedForceBy, France]
-
A.
usedForceUnder
Indicates that one entity applied or exerted force while positioned beneath or lower than another entity.
-
B.
usesForceUnder
Indicates that one entity applies physical power, coercion, or pressure to another entity while being positioned beneath or below it.
-
C.
usesForces
chosen
Indicates that one entity applies physical, magical, or other types of forces to influence, move, or affect another entity.
-
D.
inForceWith
Indicates that a rule, condition, or agreement is currently active and being applied in conjunction with a specified entity or set of entities.
-
E.
associatedForce
Indicates that there is a force linked or connected to an entity, typically representing the physical influence acting on or exerted by that 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_69f76dbde1c08190a24e7f9beb564c8d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: May 3, 2026, 4 p.m.