Triple
T4467313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antep baklavası |
E98408
|
entity |
| Predicate | usesFatType |
P40978
|
FINISHED |
| Object | clarified butter from sheep or cow 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: clarified butter from sheep or cow milk | Statement: [Antep baklavası, usesFatType, clarified butter from sheep or cow milk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFatType Context triple: [Antep baklavası, usesFatType, clarified butter from sheep or cow milk]
-
A.
typicalFatUsed
chosen
Indicates that a particular type of fat is commonly or characteristically used in a given context or application.
-
B.
typicalFatContent
Indicates the usual or characteristic amount of fat contained in something, such as a food or product.
-
C.
stomachType
Indicates the kind or classification of stomach an entity has, typically describing its structural or functional type.
-
D.
usedTractionType
Indicates the type of traction or drive mechanism that was employed in performing the action or operating the entity.
-
E.
hasStomachType
Indicates that an entity possesses or is characterized by a specific type or classification of stomach.
- 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_69b3454b4ae481908967426dd37284d6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b356fb69a0819099f0005779f4fcac |
completed | March 13, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69b3563bf4f8819081726cde3a34460b |
completed | March 13, 2026, 12:11 a.m. |
Created at: March 12, 2026, 11:34 p.m.