Triple
T14366703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jorah Mormont |
E356252
|
entity |
| Predicate | disgracedFor |
P113750
|
FINISHED |
| Object | selling poachers into slavery |
—
|
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: selling poachers into slavery | Statement: [Jorah Mormont, disgracedFor, selling poachers into slavery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disgracedFor Context triple: [Jorah Mormont, disgracedFor, selling poachers into slavery]
-
A.
associatedScandal
Indicates a relationship where an entity is linked to, involved in, or notably connected with a particular scandal.
-
B.
derogadaPor
Indicates that a law, rule, or norm has been annulled, revoked, or rendered invalid by another legal provision or authority.
-
C.
criticizedFor
Indicates that one entity expresses disapproval or negative judgment of another entity specifically because of a particular action, quality, or outcome.
-
D.
subjectOfCondemnation
Indicates that one entity is the target or object of formal disapproval, criticism, or denunciation by another entity.
-
E.
sackedBy
Indicates that one entity was dismissed or fired from a position or job by another entity.
- F. None of above. chosen
Provenance (4 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8faf00e8819087d7100e9d8c1877 |
completed | April 14, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69de2a9cb3e081909f6b33fdd939bb9e |
completed | April 14, 2026, 11:53 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:15 a.m.