Triple
T35428943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morbier cheese |
E1024000
|
entity |
| Predicate | modernAshType |
P193625
|
FINISHED |
| Object | edible vegetable ash |
—
|
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: edible vegetable ash | Statement: [Morbier cheese, modernAshType, edible vegetable ash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernAshType Context triple: [Morbier cheese, modernAshType, edible vegetable ash]
-
A.
modernVariation
Indicates that one entity is a contemporary or updated version, adaptation, or reinterpretation of another.
-
B.
modernAccess
Indicates that an entity has contemporary, up-to-date means or methods of accessing or interacting with another entity or resource.
-
C.
modernSymbol
Indicates that something functions as a contemporary or current-era symbol representing or standing for something else.
-
D.
modernBase
Indicates that one entity serves as the contemporary or current foundational basis or reference point for another entity.
-
E.
modernProduction
Indicates that something is created, manufactured, or staged using contemporary methods, technologies, or stylistic approaches.
- 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_69f76df743c48190aecb6dd79efb0d95 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
| PDg | Predicate description generation | batch_69fd4d16dd20819096957c40f43cd971 |
completed | May 8, 2026, 2:40 a.m. |
Created at: May 3, 2026, 4:03 p.m.