Triple
T30001542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Consultant |
E762180
|
entity |
| Predicate | connectedToFilm |
P92754
|
FINISHED |
| Object | The Incredible Hulk (2008 film) |
—
|
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: The Incredible Hulk (2008 film) | Statement: [The Consultant, connectedToFilm, The Incredible Hulk (2008 film)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedToFilm Context triple: [The Consultant, connectedToFilm, The Incredible Hulk (2008 film)]
-
A.
linkedToFilmStar
Indicates that one entity has a direct connection or association with a film star.
-
B.
linkedFilm
chosen
Indicates that there is an associated or connected film related to the given entity.
-
C.
associatedWithProducerOfFilm
Indicates that one entity has an association or connection with the producer of a particular film.
-
D.
associatedWithComposerOfFilm
Indicates a relationship where an entity is connected to the composer who created the musical score for a specific film.
-
E.
endedWithFilm
Indicates that an event, series, or process concluded with the showing, release, or occurrence of a particular film.
- 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_69f2246a47ac81909cf5213053687ffc |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
Created at: April 29, 2026, 6:41 p.m.