Triple
T31522400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lester Freamon |
E804242
|
entity |
| Predicate | demotedTo |
P111507
|
FINISHED |
| Object | Pawn Shop Unit |
—
|
NE NERFINISHED |
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: Pawn Shop Unit | Statement: [Lester Freamon, demotedTo, Pawn Shop Unit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demotedTo Context triple: [Lester Freamon, demotedTo, Pawn Shop Unit]
-
A.
demotedToSecondTierBy
Indicates that an entity’s status, rank, or priority has been reduced by another entity to a secondary or lower tier.
-
B.
demotes
Indicates that one entity reduces another entity’s rank, status, or level within a hierarchy or system.
-
C.
relegatedTo
chosen
Indicates that something or someone has been assigned, demoted, or confined to a lower, secondary, or less important position, status, or category.
-
D.
relegatedFrom
Indicates that an entity has been demoted, downgraded, or moved from a higher status, level, or position to a lower one, typically as a result of performance or evaluation.
-
E.
demotedTitleForDeposed
Indicates that an entity has been assigned a lower or reduced title as a result of being deposed from a former position or rank.
- 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_69f348cf839c81908657048402f7f97b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 9:56 p.m.