Triple
T27940762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sully family |
E700733
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Avatar franchise character group |
C43720
|
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: Avatar franchise character group Context triple: [Sully family, instanceOf, Avatar franchise character group]
-
A.
Avatar franchise character
chosen
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.
Star Wars family
A Star Wars family is a group of characters connected by blood, adoption, or close emotional bonds whose relationships significantly influence the saga’s central conflicts, legacies, and themes of destiny and redemption.
-
C.
Frozen franchise work
A Frozen franchise work is any creative production—such as a film, short, book, game, or related media—set in the Frozen universe and featuring its characters, themes, or settings as established by Disney’s Frozen series.
-
D.
Transformers series
The Transformers series is a multimedia franchise centered on sentient robots that can transform into vehicles, weapons, and other objects, exploring their conflicts and alliances across comics, cartoons, films, and toys.
-
E.
Terminator franchise element
A Terminator franchise element is any character, machine, event, technology, or narrative construct that originates from or is fundamentally tied to the Terminator universe’s depiction of time-traveling warfare between humans and sentient machines.
- 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
Created at: April 27, 2026, 7:17 p.m.