Triple
T36195668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Kind Diet |
E1047115
|
entity |
| Predicate | recommendsAvoiding |
P11581
|
FINISHED |
| Object | meat |
—
|
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: meat | Statement: [The Kind Diet, recommendsAvoiding, meat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recommendsAvoiding Context triple: [The Kind Diet, recommendsAvoiding, meat]
-
A.
avoidedFor
Indicates that one entity is deliberately not used, chosen, or engaged with because of the presence, influence, or characteristics of another entity.
-
B.
mustAvoid
Indicates that one entity is required to stay away from, not engage with, or prevent interaction with another entity or condition.
-
C.
seeksToAvoid
Indicates an entity’s intention or effort to stay away from, prevent, or not experience another entity or situation.
-
D.
notRecommendedIn
Indicates that something is advised against or discouraged from being used, done, or applied within a particular context, situation, or location.
-
E.
notRecommendedBy
chosen
Indicates that one entity explicitly advises against or does not endorse another entity.
- 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_69f76e414bdc8190996f15a544220a3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:08 p.m.