Triple
T31601556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quillaja family |
E806360
|
entity |
| Predicate | barkUseOfMembers |
P172014
|
FINISHED |
| Object | soap substitute |
—
|
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: soap substitute | Statement: [Quillaja family, barkUseOfMembers, soap substitute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: barkUseOfMembers Context triple: [Quillaja family, barkUseOfMembers, soap substitute]
-
A.
claimedMembers
Indicates that an entity asserts or reports that certain other entities are its members or belong to it.
-
B.
memberOwned
Indicates that an entity is owned collectively by its members rather than by external owners or shareholders.
-
C.
killsMembersOf
Indicates that one entity causes the death of individuals who belong to a particular group or organization.
-
D.
hasMembersWith
Indicates that a group or collection includes one or more specific members that satisfy a given condition or characteristic.
-
E.
eachMemberHas
Indicates that every individual element within a group or collection possesses or is associated with a specified property, attribute, or item.
- 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_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a956e9b08190bf83547bba8e8147 |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8036ab481908019f2f071fa406e |
completed | May 3, 2026, 1:42 a.m. |
Created at: April 30, 2026, 10:33 p.m.