Triple
T17911979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superman Family |
E447836
|
entity |
| Predicate | sharesTheme |
P47748
|
FINISHED |
| Object | Kryptonian heritage |
—
|
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: Kryptonian heritage | Statement: [Superman Family, sharesTheme, Kryptonian heritage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesTheme Context triple: [Superman Family, sharesTheme, Kryptonian heritage]
-
A.
sharesThemeWith
chosen
Indicates that two entities are related by having the same or closely similar underlying theme or subject matter.
-
B.
theme
Indicates the entity that is the primary participant or content affected or characterized by an action, event, or state.
-
C.
followsInTheme
Indicates that one element continues or succeeds another while maintaining the same theme or thematic context.
-
D.
followsTheme
Indicates that one entity adheres to, is guided by, or is structured according to the theme established by another entity.
-
E.
themeInspiration
Indicates that one entity serves as the creative source or conceptual basis that inspires or shapes the theme expressed in another entity.
- 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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49ea0ea008190b54a999e0704fb67 |
completed | April 19, 2026, 9:21 a.m. |
| PD | Predicate disambiguation | batch_69e3d8ec2f6881909d7f54b878cbed37 |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:19 a.m.