Triple
T28868021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Family (The Omega Man) |
E729055
|
entity |
| Predicate | activeAtTime |
P98493
|
FINISHED |
| Object | post-apocalyptic future of The Omega Man |
—
|
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: post-apocalyptic future of The Omega Man | Statement: [The Family (The Omega Man), activeAtTime, post-apocalyptic future of The Omega Man]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeAtTime Context triple: [The Family (The Omega Man), activeAtTime, post-apocalyptic future of The Omega Man]
-
A.
activeAt
chosen
Indicates that an entity is functioning, valid, or in effect during a specified time or at a particular location or context.
-
B.
activationTime
Indicates the specific point in time at which an entity, process, or function becomes active or starts operating.
-
C.
activeFrom
Indicates the starting point in time from which an entity or relationship is considered active or in effect.
-
D.
activeAfter
Indicates that one entity becomes active only after another specified event, state, or time has occurred.
-
E.
activeAs
Indicates that an entity is currently functioning or serving in a particular role, capacity, or status.
- 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 28, 2026, 6:49 a.m.