Triple
T9310642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bar Kosiba |
E223996
|
entity |
| Predicate | afterRevoltPolicy |
P33756
|
FINISHED |
| Object | Roman refounding of Jerusalem as Aelia Capitolina |
—
|
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: Roman refounding of Jerusalem as Aelia Capitolina | Statement: [Bar Kosiba, afterRevoltPolicy, Roman refounding of Jerusalem as Aelia Capitolina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterRevoltPolicy Context triple: [Bar Kosiba, afterRevoltPolicy, Roman refounding of Jerusalem as Aelia Capitolina]
-
A.
postRevolution
Indicates that one event, condition, or state occurs or exists after a revolution has taken place.
-
B.
facedRebellionBy
Indicates that an entity experienced opposition or an uprising initiated by another entity.
-
C.
aftermathPolicy
chosen
Indicates the policy, rules, or procedures that apply in the aftermath or consequences of a particular event or action.
-
D.
notableRevolt
Indicates a significant uprising or rebellion in which the subject played an important or historically notable role.
-
E.
laterPolicy
Indicates that one policy occurs or becomes effective after another policy in 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_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.