Triple
T34560618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cross Creek |
E887328
|
entity |
| Predicate | hasSupportingActorNominee |
P40640
|
FINISHED |
| Object | Rip Torn |
E68617
|
NE 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: Rip Torn | Statement: [Cross Creek, hasSupportingActorNominee, Rip Torn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSupportingActorNominee Context triple: [Cross Creek, hasSupportingActorNominee, Rip Torn]
-
A.
supportingActorNominee
chosen
Indicates that an entity has been nominated for an award recognizing their performance in a supporting acting role.
-
B.
supportingActorOfWinningFilm
Indicates that an entity is a supporting actor in a film that has won a specified award or competition.
-
C.
supportingActorAwardRecipient
Indicates that an entity has received an award specifically for a supporting acting role in a performance or production.
-
D.
hasProminentSupportingActor
Indicates that an entity (such as a film or show) features a supporting actor whose role or recognition is notably significant within that work.
-
E.
hasNomineeRole
Indicates that an entity serves in or holds a specific nominee role or position in relation to another entity.
- F. None of above.
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_69f349d0c4d881908dd0950f5eb9ec0a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff9a25407c81909faa86e72a7a9d17 |
completed | May 9, 2026, 8:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a374100d73881908095a23a3032f589 |
completed | June 21, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69ff99c613688190a03b2f93d5ccad2b |
completed | May 9, 2026, 8:32 p.m. |
Created at: May 1, 2026, 2:02 a.m.