Triple
T4331832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cheshire cheese |
E96766
|
entity |
| Predicate | moistureContent |
P42283
|
FINISHED |
| Object | relatively high for a hard cheese |
—
|
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: relatively high for a hard cheese | Statement: [Cheshire cheese, moistureContent, relatively high for a hard cheese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moistureContent Context triple: [Cheshire cheese, moistureContent, relatively high for a hard cheese]
-
A.
receivesMoistureFrom
Indicates that one entity obtains or is supplied with moisture (such as water, humidity, or precipitation) from another entity.
-
B.
dryMass
Indicates the mass of an object excluding any contained fluids, propellants, or other consumable materials.
-
C.
wetnessLevel
chosen
Indicates the degree or intensity of how wet something is in relation to a reference state or scale.
-
D.
hasAmyloseContent
Indicates that an entity (typically a food or plant material) possesses a specified amount or proportion of amylose in its starch content.
-
E.
solubilityInWater
Indicates how readily a substance dissolves in water under specified conditions.
- 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_69b34542fd908190b11b08faad8decfd |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3514dc588819086a4c6d585c1b5b1 |
completed | March 12, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69b34f4e13fc8190a42c519f37959d27 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:13 p.m.