Triple
T12600776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Role of Force in History |
E300850
|
entity |
| Predicate | positionOnForce |
P100299
|
FINISHED |
| Object | force is a tool of economic interests |
—
|
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: force is a tool of economic interests | Statement: [The Role of Force in History, positionOnForce, force is a tool of economic interests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnForce Context triple: [The Role of Force in History, positionOnForce, force is a tool of economic interests]
-
A.
axisForce
Indicates a force applied along a specific axis or direction between entities.
-
B.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
C.
positionOnPhysics
chosen
Indicates a stance, viewpoint, or opinion that one entity holds regarding the subject or field of physics.
-
D.
forceDirection
Indicates the direction in which a force is applied or exerted in the relationship between entities.
-
E.
axisForces
Indicates a relationship where one entity exerts or applies force along, around, or with respect to a particular axis defined by 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9559458dc8190bc4d6e697e99d70e |
completed | April 10, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69d9541894fc8190a0c3706a414279f0 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:09 p.m.