Triple
T37718106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infinity, Inc. |
E939507
|
entity |
| Predicate | hasLegacyTheme |
P62774
|
FINISHED |
| Object | superhero legacies |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: superhero legacies | Statement: [Infinity, Inc., hasLegacyTheme, superhero legacies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegacyTheme Context triple: [Infinity, Inc., hasLegacyTheme, superhero legacies]
-
A.
hasLegacy
Indicates that an entity leaves behind a lasting impact, influence, or inheritance that continues to exist or be recognized over time.
-
B.
hasLegacyAt
Indicates that an entity has left a lasting impact, influence, or heritage associated with a particular place or context.
-
C.
isConsideredLegacy
Indicates that something is regarded as outdated or superseded, typically maintained only for backward compatibility or historical reasons.
-
D.
hasThemeType
chosen
Indicates that something is associated with or characterized by a particular thematic category or type.
-
E.
hasLegacyProgram
Indicates that an entity is associated with a program that is based on older or previous standards, systems, or offerings that have been retained from the past.
- F. None of above.
Provenance (3 batches)
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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe9b0276d48190b554fa22b043e6d8 |
completed | May 9, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69fe999692b081909921e1148d66f0ef |
completed | May 9, 2026, 2:19 a.m. |
Created at: May 3, 2026, 4:18 p.m.