Triple
T17862384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | corbomite bluff |
E446105
|
entity |
| Predicate | fictionalSubstanceName |
P53122
|
FINISHED |
| Object | corbomite |
—
|
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: corbomite | Statement: [corbomite bluff, fictionalSubstanceName, corbomite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalSubstanceName Context triple: [corbomite bluff, fictionalSubstanceName, corbomite]
-
A.
hasFictionalSubstance
Indicates that one entity includes, contains, or involves a fictional or imaginary substance as part of its composition, setting, or narrative.
-
B.
substancePersonified
Indicates that an abstract substance or concept is represented or treated as if it were a person or sentient being.
-
C.
fictionalObject
Indicates that one entity is a fictional or imaginary object in relation to another entity.
-
D.
fictionalMaterial
chosen
Indicates that something is made of, composed of, or incorporates a material that exists only in fiction or imagination.
-
E.
fictionalLanguage
Indicates a relationship where an entity uses, is expressed in, or is associated with a language that is invented or does not exist in reality.
- 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.