Triple
T23100176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of El |
E576002
|
entity |
| Predicate | survivingMembersAfterDestruction |
P125030
|
FINISHED |
| Object | Kal-El |
—
|
NE NERFINISHED |
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: Kal-El | Statement: [House of El, survivingMembersAfterDestruction, Kal-El]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivingMembersAfterDestruction Context triple: [House of El, survivingMembersAfterDestruction, Kal-El]
-
A.
hasSurvivors
Indicates that one or more entities continue to exist or remain alive after a particular event, condition, or incident.
-
B.
survivedBy
Indicates that one entity continues to live or exist after the death or end of another entity.
-
C.
survivorsAtTimeOfDestruction
chosen
Indicates that the referenced entities were still alive or remained intact at the specific time when a particular destruction event occurred.
-
D.
isSurvivorOf
Indicates that one entity has lived through, endured, or remained alive after a particular event, condition, or harmful circumstance involving another entity.
-
E.
crewSurvivorsOnReturn
Indicates that the members of a crew remained alive and successfully returned from a mission or journey.
- 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_69e245c060b48190a9bd61a47a16db17 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18de81060819084ab618f05aae583 |
completed | April 29, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_69ef89e5ce748190b2c3ac3843484127 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:58 p.m.