Triple
T4292433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bryndza Podhalańska |
E99625
|
entity |
| Predicate | coagulationMethod |
P53134
|
FINISHED |
| Object | rennet coagulation |
—
|
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 coagulation | Statement: [Bryndza Podhalańska, coagulationMethod, rennet coagulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coagulationMethod Context triple: [Bryndza Podhalańska, coagulationMethod, rennet coagulation]
-
A.
coagulationType
chosen
Indicates the specific kind or category of coagulation process or method associated with an entity.
-
B.
mobilizationMethod
Indicates the method or process by which resources, people, or assets are organized and activated for a particular purpose or operation.
-
C.
separationMethod
Indicates the technique or process used to separate one substance, component, or entity from another.
-
D.
modalityOf
Indicates that one element specifies the manner, mood, or mode in which the action, event, or state expressed by another element is realized or presented.
-
E.
diagnosisMethod
Indicates the method, procedure, or technique used to establish or confirm a diagnosis for a condition or case.
- 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_69b3455175088190aa79c6e03b86647e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3508035a08190b752c8edce0aff86 |
completed | March 12, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69b347fe55a88190b77bab0c0f38e1aa |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:08 p.m.