Triple
T15018804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maasdam cheese |
E378027
|
entity |
| Predicate | hasHoleFormationCause |
P116416
|
FINISHED |
| Object | gas produced by bacteria |
—
|
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: gas produced by bacteria | Statement: [Maasdam cheese, hasHoleFormationCause, gas produced by bacteria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHoleFormationCause Context triple: [Maasdam cheese, hasHoleFormationCause, gas produced by bacteria]
-
A.
hasHoleShape
Indicates that an entity possesses a hole or opening characterized by a specific geometric or structural shape.
-
B.
hasHoleCount
Indicates that an entity possesses a specified number of holes.
-
C.
hasHoleVariety
Indicates that one entity possesses or exhibits a particular type or variety of hole.
-
D.
hasHoleName
Indicates that an entity (such as a golf course or layout) has a specific hole identified by a particular name.
-
E.
holePresence
Indicates the existence of a hole or perforation in or on the referenced object or material.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded76445988190984b57de66e00c4a |
completed | April 15, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69de9a67cbc481909c19c2de57de4eb7 |
completed | April 14, 2026, 7:50 p.m. |
| PDg | Predicate description generation | batch_69deb1a88d588190996afa8e5b32b552 |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:56 a.m.