Triple
T21211319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stanley Ipkiss |
E522726
|
entity |
| Predicate | alignmentInFilm |
P74485
|
FINISHED |
| Object | heroic |
—
|
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: heroic | Statement: [Stanley Ipkiss, alignmentInFilm, heroic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alignmentInFilm Context triple: [Stanley Ipkiss, alignmentInFilm, heroic]
-
A.
alignmentInSeries
Indicates that one entity’s position or orientation is arranged in a specific way relative to others within an ordered sequence or series.
-
B.
alignmentInStory
chosen
Indicates how a character’s moral or ethical stance (e.g., good, neutral, evil) is portrayed within the context of a specific story.
-
C.
alignmentShape
Indicates that one entity’s shape is arranged, oriented, or matched in position relative to another entity’s shape.
-
D.
alignmentConcept
Indicates a conceptual or abstract relationship of alignment or correspondence between entities, such as agreement, compatibility, or shared orientation in some dimension.
-
E.
alignedAgainst
Indicates that two or more entities are united in opposition to a common target, side, or objective.
- 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_69e0b511ed84819099b449b4a111085c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7346eb20c8190aeb3c0cc0a24aaf9 |
completed | April 21, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:37 p.m.