Triple
T17862393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | corbomite bluff |
E446105
|
entity |
| Predicate | truthStatusInCanon |
P62601
|
FINISHED |
| Object | a complete bluff |
—
|
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: a complete bluff | Statement: [corbomite bluff, truthStatusInCanon, a complete bluff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: truthStatusInCanon Context triple: [corbomite bluff, truthStatusInCanon, a complete bluff]
-
A.
followsInCanon
Indicates that one entity occurs later than and in continuity with another within an established narrative or canonical sequence.
-
B.
hasPlaceInCanon
chosen
Indicates that something holds a specific status or position within an established canon or authoritative body of works.
-
C.
notInCanonOf
Indicates that something is excluded from, or does not belong to, the officially recognized canon of a given work or universe.
-
D.
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.
-
E.
originDebatedInCanon
Indicates that the character’s or entity’s origin story is discussed with conflicting or unresolved explanations within the official canon.
- 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e49790ea148190b7a966812d44f430 |
completed | April 19, 2026, 8:51 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e6d2e88190ad9ef9f8a99f13e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:17 a.m.