Triple
T9310759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bethar |
E223999
|
entity |
| Predicate | roleInRevolt |
P88009
|
FINISHED |
| Object | headquarters of Bar Kokhba in final phase |
—
|
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: headquarters of Bar Kokhba in final phase | Statement: [Bethar, roleInRevolt, headquarters of Bar Kokhba in final phase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInRevolt Context triple: [Bethar, roleInRevolt, headquarters of Bar Kokhba in final phase]
-
A.
roleInMutiny
Indicates that one entity participated in a mutiny with a specific role or capacity in that rebellious action.
-
B.
roleInAmericanRevolution
Indicates that an entity had a specific role, position, or involvement in events or activities related to the American Revolution.
-
C.
typeOfRebel
Indicates that one entity is a rebel belonging to, or classified under, a particular type or category of rebellion.
-
D.
roleBeforeQuietRevolution
Indicates that an entity held a particular role or status prior to the Quiet Revolution period.
-
E.
facedRebellionBy
Indicates that an entity experienced opposition or an uprising initiated by another entity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69cc955a38108190b602d1e73725f11b |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:37 p.m.