Triple
T22755789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Octomore |
E562839
|
entity |
| Predicate | peatedWith |
P62361
|
FINISHED |
| Object | high phenol level malted barley |
—
|
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 phenol level malted barley | Statement: [Octomore, peatedWith, high phenol level malted barley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peatedWith Context triple: [Octomore, peatedWith, high phenol level malted barley]
-
A.
peated
Indicates that an action, event, or state has occurred repeatedly or multiple times.
-
B.
repetitionOf
Indicates that one entity is a repeated occurrence or instance of another entity, preserving the same content or pattern.
-
C.
usesRepetition
Indicates that one entity employs repeated elements, actions, or patterns as a deliberate feature or technique in relation to another entity or context.
-
D.
repeatedlyFormed
Indicates that the same relationship, structure, or configuration is created or occurs multiple times, often in a recurring or iterative manner.
-
E.
peatSource
chosen
Indicates that one entity serves as the origin or provider of peat for another entity or context.
- 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_69e24551ec7881909a9c924dbea155f6 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f179bd22588190ac724a656194f5b9 |
completed | April 29, 2026, 3:23 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:25 p.m.