Triple
T22461054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silk |
E555228
|
entity |
| Predicate | positionedAsAlternativeTo |
P5887
|
FINISHED |
| Object | cow's milk |
—
|
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: cow's milk | Statement: [Silk, positionedAsAlternativeTo, cow's milk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionedAsAlternativeTo Context triple: [Silk, positionedAsAlternativeTo, cow's milk]
-
A.
isAlternativeTo
chosen
Indicates that one entity can serve as a substitute or different option in place of another.
-
B.
positionedAgainst
Indicates that one entity is placed so that it directly faces or is set opposite to another entity, often in close or contacting alignment.
-
C.
alternativeUsedBy
Indicates that one entity serves as an alternative option or substitute that is used in place of another entity.
-
D.
initiallyPositionedAs
Indicates that one entity’s starting or original position is specified relative to another entity or reference frame.
-
E.
alternativeHolder
Indicates that one entity serves as an alternative or substitute holder in place of 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_69e11e51fdec8190adfdf9f8a6362221 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b7f74948190beaf6ea24ba29276 |
completed | April 29, 2026, 1:14 a.m. |
| PD | Predicate disambiguation | batch_69e898ad961c819098fd1e46129bddcc |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:48 p.m.