Triple
T34814964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joey Travolta |
E1003605
|
entity |
| Predicate | inceptionOfInclusionFilms |
P83325
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [Joey Travolta, inceptionOfInclusionFilms, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inceptionOfInclusionFilms Context triple: [Joey Travolta, inceptionOfInclusionFilms, 2007]
-
A.
includedInFilm
Indicates that one entity (such as a scene, segment, or element) is contained within or forms part of a particular film.
-
B.
inceptionWithin
Indicates that one event, process, or entity begins or is initiated entirely within the temporal or spatial bounds of another.
-
C.
beginsWithFilm
chosen
Indicates that one entity (typically a series, collection, or sequence) starts or is initiated with a particular film as its first element.
-
D.
inheritedByInFilm
Indicates that a character, role, or attribute is passed on or taken over by another character within the narrative of a film.
-
E.
inceptionBefore
Indicates that one entity’s beginning, creation, or initiation occurs earlier in time than that of 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_69f76db717088190811b4e744610f37d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ab8abd08190a7f001927cc76a8d |
completed | May 3, 2026, 4:41 p.m. |
| PD | Predicate disambiguation | batch_69f7795b1abc8190823664d1caa94649 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.