Triple
T12951470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pete Tyler |
E309901
|
entity |
| Predicate | statusInParallelUniverse |
P83186
|
FINISHED |
| Object | alive |
—
|
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: alive | Statement: [Pete Tyler, statusInParallelUniverse, alive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInParallelUniverse Context triple: [Pete Tyler, statusInParallelUniverse, alive]
-
A.
statusInManyContinuities
chosen
Indicates that an entity holds a particular status or role across multiple distinct continuities, timelines, or versions of a narrative or system.
-
B.
in-universeStatus
Indicates the canonical status or role that something holds within the fictional universe or narrative continuity itself.
-
C.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
D.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
E.
statusInUnion
Indicates the specific role, standing, or membership condition an entity holds within a larger union or collective group.
- 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_69d7bdfb57a88190836b743e2825feca |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97dba57988190b786ffed55687a72 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:43 p.m.