Triple
T29025822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tales to Astonish |
E737588
|
entity |
| Predicate | notableCharacterTeam |
—
|
GENERATED |
| Object | Avengers-related characters |
—
|
UNRECOGNIZED GENERATED |
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCharacterTeam Context triple: [Tales to Astonish, notableCharacterTeam, Avengers-related characters]
-
A.
notableCharacterGroup
chosen
Indicates that a group of characters is especially prominent, significant, or noteworthy within a given context or work.
-
B.
notableCharacterAffiliation
Indicates that a notable character is formally associated with, aligned to, or a member of a particular group, organization, or affiliation.
-
C.
notableTeamLeader
Indicates that an entity serves as a prominent or distinguished leader of a particular team.
-
D.
notableCharacterName
Indicates that the subject has a notable or significant character whose name is given by the object.
-
E.
notableTeamUnit
Indicates that an entity is a significant or distinguished member unit (such as a player or component) of a particular team.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
Created at: April 28, 2026, 9:52 a.m.