Triple
T13148417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Effie Trinket |
E312398
|
entity |
| Predicate | laterSympathizesWith |
P70674
|
FINISHED |
| Object | rebellion |
—
|
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 | Statement: [Effie Trinket, laterSympathizesWith, rebellion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterSympathizesWith Context triple: [Effie Trinket, laterSympathizesWith, rebellion]
-
A.
isSympatheticTo
chosen
Indicates that one entity feels or expresses compassion, understanding, or emotional support toward another entity.
-
B.
declaredSolidarityWith
Indicates that one entity has publicly expressed support or unity with another entity, often in relation to a cause, struggle, or shared position.
-
C.
relievedBy
Indicates that one entity eases, reduces, or removes the burden, pain, stress, or responsibility experienced by another entity.
-
D.
ally
Indicates a cooperative relationship in which one entity supports, assists, or aligns with another, often for mutual benefit or a shared goal.
-
E.
laterComplementedBy
Indicates that an earlier entity is subsequently supplemented, enhanced, or completed by a later 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bbd1d088190b7c69f37fc6eeb64 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:11 p.m.