Triple
T38143708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Who Dat Boy |
E952550
|
entity |
| Predicate | productionCharacter |
P155206
|
FINISHED |
| Object | menacing |
—
|
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: menacing | Statement: [Who Dat Boy, productionCharacter, menacing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productionCharacter Context triple: [Who Dat Boy, productionCharacter, menacing]
-
A.
producerCharacter
Indicates that a producer is responsible for or associated with a particular character in a work.
-
B.
plotCharacter
Indicates a relationship where a character plays a role or participates in the narrative plot of a story or work.
-
C.
characters
Indicates that one entity is a character (or set of characters) associated with, appearing in, or belonging to another entity (such as a work, story, or medium).
-
D.
characterPersona
chosen
Indicates that one entity embodies, represents, or assumes the persona, role, or character identity specified by another entity.
-
E.
character1
Indicates that the subject is identified as the first or primary character in a narrative or context.
- 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_69f76f09a7148190a4b91c0bacdc127a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff53389a0481908b2baeb43c6294f0 |
completed | May 9, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69ff52e2b4b88190b38d160d771fe14b |
completed | May 9, 2026, 3:29 p.m. |
Created at: May 3, 2026, 4:21 p.m.