Triple
T38468172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abondance cheese |
E912631
|
entity |
| Predicate | curdCutting |
P191162
|
FINISHED |
| Object | finely cut curd |
—
|
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: finely cut curd | Statement: [Abondance cheese, curdCutting, finely cut curd]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: curdCutting Context triple: [Abondance cheese, curdCutting, finely cut curd]
-
A.
curdType
Indicates the specific kind or category of curd associated with an entity.
-
B.
cropMilkProducedBy
Indicates that a specific quantity or type of milk is produced by a particular crop or plant source.
-
C.
cheeseType
Indicates that one entity is a specific type or variety of cheese in relation to another entity.
-
D.
roleInCheeseRind
Indicates the specific functional or structural role an entity plays in the formation, maintenance, or characteristics of a cheese rind.
-
E.
cheeseMadeFrom
Indicates that one entity is produced or derived as cheese from another entity (typically a source ingredient such as milk).
- 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_69f76e861d8c81908559031dc66e3c15 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcdaa2bfc08190beccabb0f1782d0d |
completed | May 7, 2026, 6:32 p.m. |
Created at: May 3, 2026, 4:31 p.m.