Triple
T32971238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cabot Creamery |
E843522
|
entity |
| Predicate | usesPrimaryInput |
P23083
|
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: [Cabot Creamery, usesPrimaryInput, cow's milk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPrimaryInput Context triple: [Cabot Creamery, usesPrimaryInput, cow's milk]
-
A.
primaryInput
chosen
Indicates that an entity serves as the main or principal input to a process, system, or operation.
-
B.
isPrimary
Indicates that one entity holds the main, leading, or most important role or status in relation to another entity or within a given context.
-
C.
usedInPrimary
Indicates that something serves as the main or principal context, setting, or application in which another thing is used.
-
D.
isPrimarilyUsedAs
Indicates that one entity serves mainly or most commonly in the role, function, or purpose specified by the other entity.
-
E.
hasPrimary
Indicates that one entity is designated as the main or most important instance (the primary) in relation to 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_69f3494b9fc48190bb61c955ba471275 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 1, 2026, 1:21 a.m.