Triple
T4797154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | focaccia genovese |
E106737
|
entity |
| Predicate | typicalFat |
P40978
|
FINISHED |
| Object | extra-virgin olive oil |
—
|
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: extra-virgin olive oil | Statement: [focaccia genovese, typicalFat, extra-virgin olive oil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFat Context triple: [focaccia genovese, typicalFat, extra-virgin olive oil]
-
A.
typicalFatContent
Indicates the usual or characteristic amount of fat contained in something, such as a food or product.
-
B.
typicalFatUsed
chosen
Indicates that a particular type of fat is commonly or characteristically used in a given context or application.
-
C.
typicalBodyType
Indicates that one entity is the usual or characteristic body type associated with another entity.
-
D.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
E.
typicalFigure
Indicates that one entity serves as a standard or representative example (a typical instance) of the other 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_69bd43f591c881909e5a532388b0f3f3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6b40c29c8190adab3503f8ba0145 |
completed | March 20, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69bd622f88188190a51d52ccfad3d2dd |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:22 p.m.