Triple
T12075717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prosciutto di Parma |
E287541
|
entity |
| Predicate | agingTimeRange |
P302
|
FINISHED |
| Object | 12–36 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: 12–36 months | Statement: [Prosciutto di Parma, agingTimeRange, 12–36 months]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: agingTimeRange Context triple: [Prosciutto di Parma, agingTimeRange, 12–36 months]
-
A.
agingTimeMinimum
Indicates the minimum amount of time that must elapse for something to be considered aged or matured according to a specified standard.
-
B.
agingTimeMaximum
Indicates the maximum duration for which something is allowed or expected to age before it is considered expired, mature, or no longer valid.
-
C.
locationPeriod
Indicates that an entity is associated with being at a particular location during a specified time period.
-
D.
availabilityPeriod
Indicates the time span during which something is available or valid for use.
-
E.
timePeriod
chosen
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
- 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_69d6ab4846e081908ee7bbd66a6d3459 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bf4f508190842927e7e0642235 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:48 p.m.