Triple
T6997968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roquefort |
E162264
|
entity |
| Predicate | humidityRequirement |
P37695
|
FINISHED |
| Object | high humidity in caves |
—
|
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: high humidity in caves | Statement: [Roquefort, humidityRequirement, high humidity in caves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: humidityRequirement Context triple: [Roquefort, humidityRequirement, high humidity in caves]
-
A.
preferredHumidity
chosen
Indicates the level or range of humidity that is most suitable or favored by a given entity.
-
B.
waterRequirement
Indicates the amount or conditions of water needed for an entity to grow, function, or be maintained properly.
-
C.
coolingRequirement
Indicates that an entity requires or is subject to a specific amount or type of cooling to operate within acceptable conditions.
-
D.
environmentalCondition
Indicates the state or characteristics of the surrounding physical environment that affect or describe a situation, process, or entity.
-
E.
waterTolerance
Indicates the degree to which an entity can withstand or function effectively in the presence of water.
- 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_69c68857ffc08190857dc62cd5253777 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbeef57881909245c8a5374a8111 |
completed | March 27, 2026, 7:35 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c67c94819084fdcf0398606027 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:33 p.m.