Triple
T4292428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bryndza Podhalańska |
E99625
|
entity |
| Predicate | consistency |
P47122
|
FINISHED |
| Object | spreadable |
—
|
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: spreadable | Statement: [Bryndza Podhalańska, consistency, spreadable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consistency Context triple: [Bryndza Podhalańska, consistency, spreadable]
-
A.
typicalConsistency
chosen
Indicates that one entity characteristically maintains a regular or expected level of consistency in relation to another entity or context.
-
B.
consistentWith
Indicates that one entity does not contradict and is compatible or in agreement with another entity, condition, or set of constraints.
-
C.
constant
Indicates that the relationship or value does not change across different instances, contexts, or over time.
-
D.
conserves
Indicates that an entity protects, preserves, or maintains another entity or resource in its existing state, preventing loss, damage, or depletion.
-
E.
commitment
Indicates a sustained obligation or promise that binds an entity to a course of action, relationship, or goal over time.
- 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.