Triple
T26149809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Movin' On Up |
E659782
|
entity |
| Predicate | associatedCharacterNames |
P88683
|
FINISHED |
| Object | George Jefferson |
—
|
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: George Jefferson | Statement: [Movin' On Up, associatedCharacterNames, George Jefferson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCharacterNames Context triple: [Movin' On Up, associatedCharacterNames, George Jefferson]
-
A.
associatedCharacters
Indicates that two or more characters are linked or connected through some relationship, involvement, or relevance to each other.
-
B.
relatedCharacter
Indicates that one character has a specified relationship or association with another character.
-
C.
fictionalCharacterAssociatedWith
chosen
Indicates that there is a notable connection or association between a fictional character and another entity, such as a work, creator, or universe.
-
D.
parentCharacters
Indicates that one character serves as a parent (biological, adoptive, or parental figure) to another character.
-
E.
featuresCharactersFrom
Indicates that one entity (such as a work or production) includes or presents characters originating from another entity.
- 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_69ee5bc496a88190af7deb7ab5e081de |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69fecd0a732c819097bdd3eb69b6158c |
completed | May 9, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69fecc0318d481908b5b20598a76a9fe |
completed | May 9, 2026, 5:54 a.m. |
Created at: April 26, 2026, 8:24 p.m.