Triple
T29007233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French press |
E736468
|
entity |
| Predicate | requiresGrindSize |
P176615
|
FINISHED |
| Object | coarse |
—
|
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: coarse | Statement: [French press, requiresGrindSize, coarse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresGrindSize Context triple: [French press, requiresGrindSize, coarse]
-
A.
grindType
Indicates the specific way or degree to which something is ground or milled, such as the fineness or style of grinding applied.
-
B.
grainSize
Indicates the relative coarseness or fineness of the material or particles involved in the relationship.
-
C.
hasGrainQuality
Indicates that an entity possesses a particular level or type of grain quality, characterizing the quality attributes of its grain.
-
D.
desiredSizeIndicates
Indicates that one entity specifies or reflects the preferred or intended size of another entity.
-
E.
sizeRequired
chosen
Indicates that a particular size or dimension is needed or must be met for something to be suitable, valid, or functional.
- 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: April 28, 2026, 9:39 a.m.