Triple
T8449689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pumpkin (Ringo) |
E199769
|
entity |
| Predicate | survivesEventsOfFilm |
P83428
|
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: [Pumpkin (Ringo), survivesEventsOfFilm, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivesEventsOfFilm Context triple: [Pumpkin (Ringo), survivesEventsOfFilm, true]
-
A.
filmedFor
Indicates that something was recorded or produced specifically for a particular purpose, audience, platform, or project.
-
B.
endedWithFilm
Indicates that an event, series, or process concluded with the showing, release, or occurrence of a particular film.
-
C.
includedInFilm
Indicates that one entity (such as a scene, segment, or element) is contained within or forms part of a particular film.
-
D.
basedInFilm
Indicates that something (such as a character, event, or work) is situated, set, or primarily located within the context or universe of a particular film.
-
E.
servedInTheatres
Indicates that a film or performance was publicly exhibited in movie theaters or similar cinema venues.
- 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_69ca83170f9081909cd98f55614c6476 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe44707b88190b3d8b30c45ef4496 |
completed | March 31, 2026, 3:12 p.m. |
| PD | Predicate disambiguation | batch_69cbd0f5a3648190beb53a139a2d5482 |
completed | March 31, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_69cbe30c2d088190b4cb89adb4e88273 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:09 p.m.