Triple
T13369934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krypton (TV series) |
E319033
|
entity |
| Predicate | chronologicallySetBefore |
P33474
|
FINISHED |
| Object | birth of Superman |
—
|
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: birth of Superman | Statement: [Krypton (TV series), chronologicallySetBefore, birth of Superman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicallySetBefore Context triple: [Krypton (TV series), chronologicallySetBefore, birth of Superman]
-
A.
chronologyPrecedes
chosen
Indicates that one event or state occurs earlier in time than another in a chronological sequence.
-
B.
chronologicallyAfter
Indicates that one event or state occurs later in time than another.
-
C.
chronologicallyOrdered
Indicates that the related entities are arranged in the order in which they occur in time.
-
D.
heldBefore
Indicates that one entity possessed or maintained control of something at an earlier time than another entity or event.
-
E.
locatedInTimeBefore
Indicates that one temporal event or interval occurs entirely before another in time.
- 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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dadcd79184819088948cd38d10a4a5 |
completed | April 11, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69d9a02c9abc8190b328e7bae747bfc5 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:33 p.m.