Triple
T11047949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Speech |
E261177
|
entity |
| Predicate | statusInLegendarium |
P58920
|
FINISHED |
| Object | artificial |
—
|
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: artificial | Statement: [Black Speech, statusInLegendarium, artificial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInLegendarium Context triple: [Black Speech, statusInLegendarium, artificial]
-
A.
in-universeStatus
chosen
Indicates the canonical status or role that something holds within the fictional universe or narrative continuity itself.
-
B.
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.
-
C.
roleInLegendarium
Indicates that one entity serves a particular narrative or functional role within the fictional mythos or legendarium associated with another entity.
-
D.
legendarium
Indicates a relationship where a work, element, or concept belongs to, is part of, or is defined within a particular fictional legendarium or mythic narrative universe.
-
E.
statusInRevelation
Indicates the role, condition, or standing that an entity holds within the context of a particular revelation or revealed message.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798315b988190bc565581b2664009 |
completed | April 9, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69d74407cb088190ba37c8da3d342b64 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.