Triple
T11147580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judas of Galilee |
E263706
|
entity |
| Predicate | causeOfRevolt |
P51764
|
FINISHED |
| Object | Roman tax census in Judea |
—
|
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 tax census in Judea | Statement: [Judas of Galilee, causeOfRevolt, Roman tax census in Judea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfRevolt Context triple: [Judas of Galilee, causeOfRevolt, Roman tax census in Judea]
-
A.
endCauseOfRevolt
Indicates that the subject is the cause or factor that brings a revolt or uprising to an end.
-
B.
causeOfPoliticalConflict
chosen
Indicates that one entity is the source or reason for a political conflict involving another entity.
-
C.
facedRebellionBy
Indicates that an entity experienced opposition or an uprising initiated by another entity.
-
D.
notableRevolt
Indicates a significant uprising or rebellion in which the subject played an important or historically notable role.
-
E.
causeOfExile
Indicates the reason or circumstance that led to an entity’s exile.
- 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e86e9ef48190b4df4b14319a954f |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75ce71944819089eee9b5c9283cbd |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:28 p.m.