Triple
T25443396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sentinel Prime |
E637565
|
entity |
| Predicate | laterAffiliationInFilm |
P169517
|
FINISHED |
| Object | Decepticons |
—
|
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: Decepticons | Statement: [Sentinel Prime, laterAffiliationInFilm, Decepticons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterAffiliationInFilm Context triple: [Sentinel Prime, laterAffiliationInFilm, Decepticons]
-
A.
laterCastMember
Indicates that one entity joined the cast of a show, film, or production at a later time than another cast member.
-
B.
followedByInFilm
Indicates that one scene, shot, or event in a film immediately succeeds another in the narrative or editing sequence.
-
C.
followsInFilmography
Indicates that one work in a person’s filmography comes after another in chronological or credited order.
-
D.
laterAppearancesIn
Indicates that one entity makes additional or subsequent appearances in relation to another entity after an initial occurrence.
-
E.
associatedWithLeadActorOfFilm
Indicates a relationship where one entity is connected or linked in some relevant way to the lead actor of a specified film.
- F. None of above. chosen
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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f67fc237608190b6542b56038a7fe4 |
completed | May 2, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f0353c88190a05b2db449abe0f4 |
completed | May 2, 2026, 10:47 p.m. |
Created at: April 21, 2026, 2 p.m.