Triple
T5498677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comté cheese |
E144272
|
entity |
| Predicate | agingTimeMaximum |
P65089
|
FINISHED |
| Object | 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: 36 months | Statement: [Comté cheese, agingTimeMaximum, 36 months]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: agingTimeMaximum Context triple: [Comté cheese, agingTimeMaximum, 36 months]
-
A.
queueWaitingTimeMaximum
Indicates the maximum amount of time an entity is allowed or expected to wait in a queue before being served or processed.
-
B.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
C.
intendedDuration
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
-
D.
longestDurationAt
Indicates that one entity has the greatest length of time associated with a particular state, event, or activity compared to other relevant entities.
-
E.
timeToComplete
Indicates the duration required for an entity or process to be fully completed.
- 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_69c008f5a2748190bce7a39aabf87a6d |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f08c2a4819093e772a1497c7ecc |
completed | March 22, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69c01b052f3c81909f71c6add0f35a6f |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f051e508190b3886d87b4afdd0b |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:32 p.m.