Triple
T29329080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rubber duck comet |
E743728
|
entity |
| Predicate | hasDetectedMolecules |
P193057
|
FINISHED |
| Object | organic compounds |
—
|
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: organic compounds | Statement: [rubber duck comet, hasDetectedMolecules, organic compounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDetectedMolecules Context triple: [rubber duck comet, hasDetectedMolecules, organic compounds]
-
A.
hasMolecularity
Indicates the number of reactant species that participate simultaneously in a single elementary reaction step.
-
B.
usesMolecule
Indicates that one entity employs or utilizes a particular molecule in performing an action, process, or function.
-
C.
hasModeOfDetection
Indicates that one entity is identified, measured, or observed using a specified method or technique of detection.
-
D.
hasMolecularWeight
Indicates that an entity possesses a specific molecular weight value, typically expressed in standardized units such as daltons or g/mol.
-
E.
hasLigand
Indicates that an entity is bound to, associated with, or interacts specifically with a particular ligand.
- 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69fd37b45b4481908b947b52fbcb7ade |
completed | May 8, 2026, 1:09 a.m. |
Created at: April 28, 2026, 1:28 p.m.