Triple
T31064447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bar Kokhba forces |
E791628
|
entity |
| Predicate | lastStrongholdFell |
P89841
|
FINISHED |
| Object | Betar |
—
|
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: Betar | Statement: [Bar Kokhba forces, lastStrongholdFell, Betar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastStrongholdFell Context triple: [Bar Kokhba forces, lastStrongholdFell, Betar]
-
A.
isLastMajorStrongholdOf
chosen
Indicates that a location serves as the final significant defensive or strategic base controlled by a particular entity.
-
B.
currentStronghold
Indicates that an entity currently serves as the primary base, fortress, or central stronghold for another entity.
-
C.
surrenderedStronghold
Indicates that one party has given up control or possession of a fortified position or stronghold to another party, typically as a result of defeat, negotiation, or coercion.
-
D.
primaryStronghold
Indicates that one location serves as the main base, fortress, or central stronghold for an entity compared to its other sites.
-
E.
strongholdOf
Indicates that a location serves as a primary fortified base, center of power, or main stronghold for a particular 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_69f224cc0c5c81908404f087bff92997 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:01 p.m.