Triple
T24233481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sleight |
E601802
|
entity |
| Predicate | mainCharacterActivity |
P55097
|
FINISHED |
| Object | drug dealing |
—
|
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: drug dealing | Statement: [Sleight, mainCharacterActivity, drug dealing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCharacterActivity Context triple: [Sleight, mainCharacterActivity, drug dealing]
-
A.
mainProtagonistHome
Indicates the primary residence or home location associated with the main protagonist in a narrative or work.
-
B.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
C.
mainMortalCharacter
Indicates that the referenced entity serves as the primary mortal (non-immortal) character in the context of a story or narrative.
-
D.
leadCharacterActivity
chosen
Indicates that an activity is performed by, associated with, or characteristic of the lead character in a narrative or work.
-
E.
mainCharacterCodeNumber
Indicates that an entity is identified as the primary or central character by a specific code number.
- 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_69e29538aafc8190a2386fdebbd1393b |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f28a99889c819080efdec76be04646 |
completed | April 29, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:02 a.m.