Triple
T9310620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bar Kosiba |
E223996
|
entity |
| Predicate | revoltAim |
P9027
|
FINISHED |
| Object | independence of Judea from Rome |
—
|
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: independence of Judea from Rome | Statement: [Bar Kosiba, revoltAim, independence of Judea from Rome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revoltAim Context triple: [Bar Kosiba, revoltAim, independence of Judea from Rome]
-
A.
warAim
chosen
Indicates the strategic objective or intended outcome that a party seeks to achieve through engaging in war or armed conflict.
-
B.
aimingMethod
Indicates the technique or approach used to direct or aim an action, object, or effect toward a target.
-
C.
fireControlSystem
Indicates a relationship where a system monitors, directs, and coordinates the detection, targeting, and firing of weapons or other actuators to control the application of force or energy.
-
D.
gunStabilisation
Indicates that an entity performs or provides stabilization for a gun, reducing its movement or recoil to improve accuracy.
-
E.
rocketArmament
Indicates that an entity is equipped with or carries rocket-based weaponry as part of its armament.
- 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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd20ac17488190aa6acf7a61420632 |
completed | April 1, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:37 p.m.