Triple
T28038621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P-body |
E708477
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Portal series character |
C4830
|
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: Portal series character Context triple: [P-body, instanceOf, Portal series character]
-
A.
Nintendo character
A Nintendo character is a fictional persona created or licensed by Nintendo that appears in its video games, media, and related merchandise, often embodying distinctive abilities, personalities, and roles within their respective game worlds.
-
B.
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.
-
C.
Resident Evil character
A Resident Evil character is an individual within the franchise’s universe who navigates bioterror outbreaks, confronts mutated creatures, and advances the overarching narrative of survival horror.
-
D.
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.
-
E.
video game character
chosen
A video game character is a fictional, interactive entity within a game world that the player controls or encounters, defined by its abilities, appearance, behavior, and role in the game's narrative or mechanics.
- F. None of above.
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_69ef9b6cf538819094a633ffa67afec1 |
completed | April 27, 2026, 5:22 p.m. |
Created at: April 27, 2026, 8:23 p.m.