Triple
T32164551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Specs |
E821526
|
entity |
| Predicate | isAliveInCanon |
P173654
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Specs, isAliveInCanon, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAliveInCanon Context triple: [Specs, isAliveInCanon, true]
-
A.
eraInCanon
Indicates that a subject belongs to, occurs within, or is classified as part of a specific era defined in a canon or fictional continuity.
-
B.
hasPlaceInCanon
Indicates that something holds a specific status or position within an established canon or authoritative body of works.
-
C.
activeInFictionalUniverse
Indicates that an entity participates, operates, or has a role within a specified fictional universe or setting.
-
D.
followsInCanon
Indicates that one entity occurs later than and in continuity with another within an established narrative or canonical sequence.
-
E.
isSetInFictionalUniverse
Indicates that a narrative work takes place within a specific fictional universe or setting.
- F. None of above. chosen
Provenance (4 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_69f3490699a48190bbef96b198e8fade |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ba1e9d5c81908ba549e95fca3c93 |
completed | May 3, 2026, 2:59 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:33 a.m.