Triple
T5143270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Connor |
E116010
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Terminator franchise character |
C2757
|
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: Terminator franchise character Context triple: [John Connor, instanceOf, Terminator franchise character]
-
A.
Star Trek character
A Star Trek character is an individual—human, alien, or artificial—who exists within the Star Trek universe and contributes to its stories through their role, relationships, and development across various series and films.
-
B.
Toho character
A Toho character is a fictional entity originating from Toho-produced media, such as kaiju films or related works, defined by its unique traits, abilities, and narrative role within the Toho universe.
-
C.
film character
chosen
A film character is a fictional or real-life persona portrayed within a movie’s narrative, defined by their traits, motivations, relationships, and actions that drive the story forward.
-
D.
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.
-
E.
film franchise
A film franchise is a series of related movies, often sharing characters, settings, or a fictional universe, produced under a common title or brand.
- 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_69bd4446c0e08190a7c29dc74976bf03 |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:43 p.m.