Triple
T19334693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leaving Home |
E483590
|
entity |
| Predicate | associatedWithCharacterOrigin |
P34184
|
FINISHED |
| Object | Superman origin story |
—
|
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: Superman origin story | Statement: [Leaving Home, associatedWithCharacterOrigin, Superman origin story]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCharacterOrigin Context triple: [Leaving Home, associatedWithCharacterOrigin, Superman origin story]
-
A.
characterOrigin
chosen
Indicates the source, background, or initial context from which a character originates.
-
B.
associatedWithCharacterAlias
Indicates that one entity is linked to or connected with an alternative name or alias used for a particular character.
-
C.
associatedWithCharacterFamily
Indicates a relationship where something is linked or connected to a particular character’s family.
-
D.
originOfCharacter
Indicates the source or place from which a character originates or is created.
-
E.
associatedWithCharacterRole
Indicates that one entity has a connection or linkage to a specific character role played or held by 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e61644b80c819080f9bca086424a36 |
completed | April 20, 2026, 12:04 p.m. |
| PD | Predicate disambiguation | batch_69e4dd12303c8190a2027c062b2dff40 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:33 p.m.