Triple
T6997906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parmigiano Reggiano |
E162263
|
entity |
| Predicate | agingCommon |
P74136
|
FINISHED |
| Object | 24 months |
—
|
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: 24 months | Statement: [Parmigiano Reggiano, agingCommon, 24 months]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: agingCommon Context triple: [Parmigiano Reggiano, agingCommon, 24 months]
-
A.
agingMethod
Indicates the process or technique by which something (typically a product or material) is matured, aged, or allowed to develop its characteristics over time.
-
B.
agingCategory
Indicates the classification of an entity based on its stage or degree of aging.
-
C.
agingPotential
Indicates the capacity or suitability of something to improve, develop, or remain effective over time as it ages.
-
D.
activeAround
Indicates that an entity is performing actions or exhibiting activity in the vicinity of another entity or location.
-
E.
seeksEngagementWith
Indicates an entity’s active effort or intention to initiate or maintain interaction, involvement, or responsive connection with another entity.
- 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_69c68857ffc08190857dc62cd5253777 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbeef57881909245c8a5374a8111 |
completed | March 27, 2026, 7:35 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c67c94819084fdcf0398606027 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8c48ba48190b8d3aa7b8d22816b |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:33 p.m.