Triple
T33739098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kevin the Teenager |
E864509
|
entity |
| Predicate | parentCharacters |
P194199
|
FINISHED |
| Object | Kevin’s mum |
—
|
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: Kevin’s mum | Statement: [Kevin the Teenager, parentCharacters, Kevin’s mum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentCharacters Context triple: [Kevin the Teenager, parentCharacters, Kevin’s mum]
-
A.
associatedCharacters
Indicates that two or more characters are linked or connected through some relationship, involvement, or relevance to each other.
-
B.
featuresCharactersFrom
Indicates that one entity (such as a work or production) includes or presents characters originating from another entity.
-
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.
mainCharactersAre
Indicates that the specified entities serve as the primary or central characters in a narrative or work.
-
E.
metCharacter
Indicates that one entity has encountered or been introduced to another entity at least once.
- 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_69f3498b24b8819096a65009e521d0e1 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
| PDg | Predicate description generation | batch_69fd67182c348190aa84a02e08dbf4e1 |
completed | May 8, 2026, 4:31 a.m. |
Created at: May 1, 2026, 1:44 a.m.