Triple
T35596021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bleu de Gex |
E1028632
|
entity |
| Predicate | mainCoagulation |
P74139
|
FINISHED |
| Object | rennet |
—
|
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: rennet | Statement: [Bleu de Gex, mainCoagulation, rennet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCoagulation Context triple: [Bleu de Gex, mainCoagulation, rennet]
-
A.
coagulationType
Indicates the specific kind or category of coagulation process or method associated with an entity.
-
B.
coagulationTime
Indicates the duration required for a substance, typically a liquid like blood or a solution, to undergo coagulation and form a solid or semi-solid clot.
-
C.
coagulationAgent
chosen
Indicates that one entity serves as or contains a substance that promotes or causes the coagulation (clotting or thickening) of another entity.
-
D.
mainMediator
Indicates that an entity serves as the primary intermediary or facilitator through which interaction, communication, or influence between other entities is conducted.
-
E.
warfarinTargetINR
Indicates the intended or prescribed International Normalized Ratio (INR) range that warfarin therapy is aiming to achieve in a patient.
- 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: May 3, 2026, 4:05 p.m.