Triple
T34100170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudy International |
E874544
|
entity |
| Predicate | usesStoryOf |
P104194
|
FINISHED |
| Object | Rudy Ruettiger |
—
|
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: Rudy Ruettiger | Statement: [Rudy International, usesStoryOf, Rudy Ruettiger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesStoryOf Context triple: [Rudy International, usesStoryOf, Rudy Ruettiger]
-
A.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
B.
worksOnStoryAbout
Indicates that one entity is actively engaged in creating, developing, or contributing to a story whose subject or focus is another entity.
-
C.
originStoryIncludes
Indicates that an entity’s origin story contains, involves, or features the referenced element as a component or part of that backstory.
-
D.
usesCoverStory
Indicates that one entity employs a false or misleading explanation or narrative to conceal its true intentions, identity, or activities from another entity.
-
E.
retellsStoryOf
chosen
Indicates that one entity recounts or narrates the story originally told or experienced by 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: May 1, 2026, 1:53 a.m.