Triple
T28579360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oaxacan cheese |
E723328
|
entity |
| Predicate | typicalUseForm |
P12789
|
FINISHED |
| Object | shredded |
—
|
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: shredded | Statement: [Oaxacan cheese, typicalUseForm, shredded]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalUseForm Context triple: [Oaxacan cheese, typicalUseForm, shredded]
-
A.
typicalForm
chosen
Indicates that one entity represents the standard, characteristic, or most common form or shape in which another entity typically appears or is realized.
-
B.
usesForm
Indicates that one entity employs, applies, or operates through a particular form, format, or structured representation of something.
-
C.
typicalUsageFormat
Indicates the usual or standard way in which something is expressed, presented, or formatted in practice.
-
D.
standardFormUsedIn
Indicates that a particular standard form is employed or applied within a given context, process, or system.
-
E.
typicalScriptForm
Indicates the usual or standard written script or notation in which something is commonly represented.
- 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_69f01d7e97708190ae9e77ee66a68abd |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a00c59b03dc8190870f0dd24603a1ef |
completed | May 10, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_6a00c5178bc88190b2a0e03f38314035 |
completed | May 10, 2026, 5:49 p.m. |
Created at: April 28, 2026, 4:14 a.m.