Triple
T3957622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pecorino Sardo |
E85818
|
entity |
| Predicate | typicalAgingTime |
P53135
|
FINISHED |
| Object | several weeks for fresh type |
—
|
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: several weeks for fresh type | Statement: [Pecorino Sardo, typicalAgingTime, several weeks for fresh type]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAgingTime Context triple: [Pecorino Sardo, typicalAgingTime, several weeks for fresh type]
-
A.
typicalConsumptionAge
Indicates the age at which something is most commonly or normally consumed.
-
B.
ageProgression
Indicates a temporal relationship where an entity’s age increases or advances over time.
-
C.
lifespan
Indicates the duration of time between an entity’s birth (or creation) and its death (or end).
-
D.
ageModel
Indicates a relationship where one entity specifies or provides the age of another entity, typically in terms of a particular age value or age-related classification.
-
E.
turnedSenior
Indicates that an entity has transitioned into senior status or a senior role relative to a previous state or position.
- 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_69aed93a96908190bcbdbfa718f155bd |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaa5afdc8190b709af2473d75d02 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8ed04e4819096bced8971cd888d |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefaa3c6a08190bfe76629c7c98eea |
completed | March 9, 2026, 4:51 p.m. |
Created at: March 9, 2026, 3:31 p.m.