Triple
T9740304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luxo Jr. |
E236168
|
entity |
| Predicate | hasNoDialogue |
P49712
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Luxo Jr., hasNoDialogue, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoDialogue Context triple: [Luxo Jr., hasNoDialogue, true]
-
A.
hasNoSpokenDialogue
chosen
Indicates that the referenced entity does not produce any spoken dialogue within the given context or work.
-
B.
hasDialogueTrait
Indicates that an entity possesses a specific characteristic or quality related to dialogue or conversational behavior.
-
C.
hasDialogueFunction
Indicates that an utterance or segment of discourse serves a specific communicative role or function within a dialogue (e.g., question, answer, request, acknowledgment).
-
D.
hasProseDialogue
Indicates that one entity contains or features spoken or conversational content expressed in prose form involving another entity.
-
E.
doesNotFeatureCharacterDirectly
Indicates that the subject work does not include the specified character as an on-screen, on-page, or otherwise directly appearing participant in its content.
- 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_69ca84d313e88190983ee6ffd0ef60d2 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9f29a5bc8190b2b391017405c71e |
completed | April 1, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69cd03cc128c81908b84ef224f858b4e |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:22 p.m.