Triple
T36195773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bear Blu Jarecki |
E1047118
|
entity |
| Predicate | hasDietReportedByMother |
P199801
|
FINISHED |
| Object | plant-based diet |
—
|
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: plant-based diet | Statement: [Bear Blu Jarecki, hasDietReportedByMother, plant-based diet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDietReportedByMother Context triple: [Bear Blu Jarecki, hasDietReportedByMother, plant-based diet]
-
A.
hasMummy
Indicates that an entity possesses or is associated with a mummy (preserved dead body).
-
B.
hasMotherOrigin
Indicates that an entity’s origin, source, or lineage is derived from or attributed to a mother entity.
-
C.
motherStatus
Indicates the current condition, role, or state of an entity in relation to being a mother (e.g., whether and how they are functioning or recognized as a mother).
-
D.
hasNutritionalConcern
Indicates that an entity is associated with a specific nutritional issue, risk, or dietary concern.
-
E.
motherWas
Indicates that one entity was the mother (biological or adoptive) of another entity at some time in the past.
- F. None of above. chosen
Provenance (4 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_69ff5803c02c81908b63067119f5e684 |
completed | May 9, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69ff576d8b308190b49a1e072a0ae661 |
completed | May 9, 2026, 3:49 p.m. |
| PDg | Predicate description generation | batch_69ff58031bb081909fea985b16f69da4 |
completed | May 9, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:08 p.m.