Triple
T32067156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cornelius |
E818911
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | character in the Planet of the Apes franchise |
C60756
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: character in the Planet of the Apes franchise Context triple: [Cornelius, instanceOf, character in the Planet of the Apes franchise]
-
A.
Avatar franchise character
An Avatar franchise character is an individual, creature, or spirit from the Avatar universe whose identity, abilities, and relationships are shaped by the world’s elemental bending, cultures, and ongoing conflicts.
-
B.
role in animated film franchise
A role in an animated film franchise represents a recurring character position or function—such as hero, sidekick, or mentor—consistently portrayed across multiple installments to maintain narrative continuity and brand identity.
-
C.
Jurassic Park character
A Jurassic Park character is an individual—human or dinosaur—whose actions, traits, and relationships drive the narrative of survival, science, and chaos within the dinosaur-filled Jurassic Park universe.
-
D.
Star Wars role
A Star Wars role is a specific character position or archetype within the Star Wars universe, defined by its narrative function, abilities, affiliations, and relationships to other characters and factions.
-
E.
character in the Robot series
A character in the Robot series is an individual—human, robot, or other sentient entity—whose actions, decisions, and interactions drive the exploration of robotics, ethics, and society within Asimov’s interconnected universe.
- F. None of above. chosen
Provenance (1 batch)
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. |
Created at: May 1, 2026, 12:22 a.m.