Triple
T23003038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edam cheese |
E572682
|
entity |
| Predicate | agingProperties |
P2072
|
FINISHED |
| Object | good keeping qualities |
—
|
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: good keeping qualities | Statement: [Edam cheese, agingProperties, good keeping qualities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: agingProperties Context triple: [Edam cheese, agingProperties, good keeping qualities]
-
A.
eligibleProperties
Indicates that certain properties meet the required conditions or criteria to qualify for a specified purpose or status.
-
B.
agingPotential
chosen
Indicates the capacity or suitability of something to improve, develop, or remain effective over time as it ages.
-
C.
agingCommon
Indicates that the entities share a common or typical pattern, process, or characteristic related to aging.
-
D.
artifactProperty
Indicates that an artifact possesses a specific property, characteristic, or attribute.
-
E.
universalProperty
Indicates that a property or characteristic holds for all members of a specified set or domain without exception.
- 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f183549bdc81908fdcd44e2c92f7c4 |
completed | April 29, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:50 p.m.