Triple
T26701313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CPH4 |
E673161
|
entity |
| Predicate | chemicalFormInFiction |
P55739
|
FINISHED |
| Object | blue crystalline powder |
—
|
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: blue crystalline powder | Statement: [CPH4, chemicalFormInFiction, blue crystalline powder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chemicalFormInFiction Context triple: [CPH4, chemicalFormInFiction, blue crystalline powder]
-
A.
hasFictionalSubstance
chosen
Indicates that one entity includes, contains, or involves a fictional or imaginary substance as part of its composition, setting, or narrative.
-
B.
chemicalComponent
Indicates that one entity is a constituent chemical part or ingredient of another entity.
-
C.
keyChemicalDiscussed
Indicates that a particular chemical substance is a central topic of discussion in a given context or communication.
-
D.
chemicalElement
Indicates that one entity is a chemical element that constitutes, characterizes, or is otherwise fundamentally associated with the other entity.
-
E.
commonChemistry
Indicates that two entities share similar or related chemical properties, composition, or behavior.
- 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_69eecda2b49c8190a6c481cfc4c07954 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61780706c8190bb9eb3d467d9f852 |
completed | May 2, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:31 a.m.