Triple
T37935706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bugey cheese |
E946341
|
entity |
| Predicate | typicallyMaturedIn |
P86480
|
FINISHED |
| Object | cellars |
—
|
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: cellars | Statement: [Bugey cheese, typicallyMaturedIn, cellars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyMaturedIn Context triple: [Bugey cheese, typicallyMaturedIn, cellars]
-
A.
maturesIn
chosen
Indicates that an entity reaches full development, ripeness, or maturity within a specified time period or under certain conditions.
-
B.
mustBeMaturedIn
Indicates that something is required to undergo a maturation process within a specified context, condition, or environment before it is considered ready or valid.
-
C.
maturedUnder
Indicates that one entity developed, grew, or reached maturity under the guidance, influence, or conditions provided by another entity.
-
D.
maturityType
Indicates the kind or category of maturity associated with an entity, such as how or when an obligation, product, or process reaches its full or due state.
-
E.
hasMaturity
Indicates that an entity possesses a specified level, state, or stage of development or maturity.
- 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.