Triple
T33284286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tabor |
E852136
|
entity |
| Predicate | featuredConflict |
P1406
|
FINISHED |
| Object | rebellion against Queen Ravenna |
—
|
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: rebellion against Queen Ravenna | Statement: [Tabor, featuredConflict, rebellion against Queen Ravenna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredConflict Context triple: [Tabor, featuredConflict, rebellion against Queen Ravenna]
-
A.
loreConflict
Indicates that there is an inconsistency, contradiction, or incompatibility between pieces of lore or canonical information.
-
B.
conflictIn
chosen
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
C.
depictsConflict
Indicates that one entity visually represents or portrays a situation of conflict involving another entity or entities.
-
D.
mainConflict
Indicates the primary opposing force, problem, or struggle that drives tension and narrative progression between entities or sides.
-
E.
conflictGround
Indicates that one entity is the cause, basis, or subject matter of a conflict involving another 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_69f349660ff48190a4568803d0b89941 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a018f9c7cf88190adc5daf3806f2077 |
completed | May 11, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_6a018ca4e0e481908091f0c1f8a4c31b |
completed | May 11, 2026, 8 a.m. |
Created at: May 1, 2026, 1:32 a.m.