Triple
T13908748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manchego cheese |
E334428
|
entity |
| Predicate | minimumAgingTime |
P65088
|
FINISHED |
| Object | 30 days |
—
|
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: 30 days | Statement: [Manchego cheese, minimumAgingTime, 30 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minimumAgingTime Context triple: [Manchego cheese, minimumAgingTime, 30 days]
-
A.
agingTimeMinimum
chosen
Indicates the minimum amount of time that must elapse for something to be considered aged or matured according to a specified standard.
-
B.
minimumAgingTotal
Indicates that the relationship captures the smallest possible total amount of aging (or elapsed time) accumulated across the relevant entities or process.
-
C.
typicalAgingTime
Indicates the usual duration required for something to age or mature under normal conditions.
-
D.
maximumAgeRequirement
Indicates that there is an upper age limit that an entity must not exceed in order for a condition, participation, or eligibility to apply.
-
E.
agingTimeMaximum
Indicates the maximum duration for which something is allowed or expected to age before it is considered expired, mature, or no longer 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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2721ec6c8190888f4a9d004eb8e0 |
completed | April 14, 2026, 11:38 a.m. |
| PD | Predicate disambiguation | batch_69dd464b1ab48190ae50bfc902bf6ef7 |
completed | April 13, 2026, 7:38 p.m. |
Created at: April 9, 2026, 10:16 p.m.