Triple
T32069071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Incredibles: Rise of the Underminer |
E818961
|
entity |
| Predicate | featuresBoss |
P126648
|
FINISHED |
| Object | The Underminer |
—
|
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 Underminer | Statement: [The Incredibles: Rise of the Underminer, featuresBoss, The Underminer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresBoss Context triple: [The Incredibles: Rise of the Underminer, featuresBoss, The Underminer]
-
A.
featuresNewBosses
Indicates that something introduces or includes newly appearing boss characters.
-
B.
featuresMonster
Indicates that something includes or prominently presents a monster as part of its content or composition.
-
C.
bossFeature
Indicates that one entity serves as a primary or dominant feature, element, or component in relation to another.
-
D.
featuresHero
Indicates that something (such as a work, product, or story) prominently includes or centers around a particular hero as a main character or focus.
-
E.
stageBossOf
chosen
Indicates that one entity serves as the primary boss or main adversary encountered in a particular stage, level, or area associated with 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a00b34364448190b8c9948d5a24d845 |
completed | May 10, 2026, 4:33 p.m. |
| PD | Predicate disambiguation | batch_6a00b2e4f13c819081bac7d763c414ad |
completed | May 10, 2026, 4:31 p.m. |
Created at: May 1, 2026, 12:23 a.m.