Triple
T32061485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pixar logo animation |
E818758
|
entity |
| Predicate | showsAction |
P162840
|
FINISHED |
| Object | Luxo Jr. hopping across the screen |
—
|
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: Luxo Jr. hopping across the screen | Statement: [Pixar logo animation, showsAction, Luxo Jr. hopping across the screen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showsAction Context triple: [Pixar logo animation, showsAction, Luxo Jr. hopping across the screen]
-
A.
showsThat
Indicates that one entity demonstrates, proves, or provides evidence for the truth or validity of another.
-
B.
showType
Indicates the category or format in which something is presented or displayed (e.g., type of show, presentation, or display mode).
-
C.
showState
Indicates that an entity presents or reveals the current condition, status, or situation of another entity.
-
D.
showsScene
chosen
Indicates that one entity (such as a media item or visual representation) depicts or presents a particular scene.
-
E.
shows
Indicates that one entity presents, displays, or makes another entity visible or known to an audience or observer.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b4f638908190957f64096c07535f |
completed | May 3, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69f6b154b3dc819087115f5f63f7b00f |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:22 a.m.