Triple
T8394654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queijo Nisa |
E198023
|
entity |
| Predicate | coagulant |
P74139
|
FINISHED |
| Object | animal 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: animal rennet | Statement: [Queijo Nisa, coagulant, animal rennet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coagulant Context triple: [Queijo Nisa, coagulant, animal rennet]
-
A.
coagulationAgent
chosen
Indicates that one entity serves as or contains a substance that promotes or causes the coagulation (clotting or thickening) of another entity.
-
B.
coagulationType
Indicates the specific kind or category of coagulation process or method associated with an entity.
-
C.
catalyst
Indicates that one entity facilitates or accelerates a process, reaction, or change involving another entity without itself being consumed or fundamentally altered.
-
D.
glaze
Indicates that an agent coats or covers a surface of an entity with a smooth, often shiny or protective, layer or substance.
-
E.
reactant
Indicates that an entity participates as a starting material or input substance in a chemical or reactive process.
- 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_69ca82f816bc8190ab321c07d72208c1 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb8185ef60819085cfa7491d35834a |
completed | March 31, 2026, 8:10 a.m. |
| PD | Predicate disambiguation | batch_69cb70d24b248190a326aa6804f942b5 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:03 p.m.