Triple
T31064841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gregory the Patrician |
E791638
|
entity |
| Predicate | reasonForRevolt |
P107944
|
FINISHED |
| Object | opposition to imperial religious policies |
—
|
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: opposition to imperial religious policies | Statement: [Gregory the Patrician, reasonForRevolt, opposition to imperial religious policies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForRevolt Context triple: [Gregory the Patrician, reasonForRevolt, opposition to imperial religious policies]
-
A.
endCauseOfRevolt
Indicates that the subject is the cause or factor that brings a revolt or uprising to an end.
-
B.
motiveForUprising
chosen
Indicates that a particular factor, condition, or event serves as a motivating cause or justification for an uprising or rebellion.
-
C.
facedRebellionBy
Indicates that an entity experienced opposition or an uprising initiated by another entity.
-
D.
actsOfRebellion
Indicates actions that deliberately oppose, resist, or defy an established authority, rule, or controlling force.
-
E.
notableRevolt
Indicates a significant uprising or rebellion in which the subject played an important or historically notable role.
- 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_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: April 29, 2026, 9:01 p.m.