Triple
T33841175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | arachidonic acid |
E867360
|
entity |
| Predicate | isCommonlyAddedTo |
P102144
|
FINISHED |
| Object | baby formulas |
—
|
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: baby formulas | Statement: [arachidonic acid, isCommonlyAddedTo, baby formulas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommonlyAddedTo Context triple: [arachidonic acid, isCommonlyAddedTo, baby formulas]
-
A.
commonAdditions
chosen
Indicates that one entity typically occurs together with or is frequently added to another as a common accompaniment or enhancement.
-
B.
isFamouslyUsedIn
Indicates that something is widely recognized or well-known for being used in a particular context, work, or situation.
-
C.
isFamouslyUsedBy
Indicates that something is widely and notably used by a particular person, group, or entity, in a way that is broadly recognized or associated with them.
-
D.
widelyUsedIn
Indicates that something is commonly or extensively utilized within a particular context, domain, or group.
-
E.
commonlyFoundOn
Indicates that one entity is typically or frequently located on, attached to, or present upon another entity.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: May 1, 2026, 1:47 a.m.