Triple
T33841158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | arachidonic acid |
E867360
|
entity |
| Predicate | doubleBonds |
P177775
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [arachidonic acid, doubleBonds, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doubleBonds Context triple: [arachidonic acid, doubleBonds, 4]
-
A.
doubleCrosses
Indicates that one party betrays another by secretly switching allegiance or undermining them after initially appearing loyal.
-
B.
bondsFormed
Indicates that a connection or attachment has been created between two or more entities.
-
C.
dualPair
Indicates that two entities form a dual pair, standing in a mathematically defined dual relationship where each is the dual counterpart of the other.
-
D.
numberOfDoubleGreens
Indicates the count of instances where two green-related elements or conditions occur together within a given context.
-
E.
formsDoubleDwarfPlanetSystemWith
Indicates that one celestial body and another together constitute a double dwarf planet system, mutually orbiting a common center of mass rather than one simply orbiting the other.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: May 1, 2026, 1:47 a.m.