Triple
T6205127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sapindaceae |
E138725
|
entity |
| Predicate | someMembersAre |
P66630
|
FINISHED |
| Object | toxic to humans |
—
|
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: toxic to humans | Statement: [Sapindaceae, someMembersAre, toxic to humans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: someMembersAre Context triple: [Sapindaceae, someMembersAre, toxic to humans]
-
A.
manyMembersAre
Indicates that a large number of members within a group possess a specified property or participate in a particular role or condition.
-
B.
someMembersAlignment
chosen
Indicates that at least one member of a group or collection has a particular alignment or orientation with respect to some criterion or reference.
-
C.
hasMembers
Indicates that a group, organization, or collection includes certain entities as its members.
-
D.
allMembersAre
Indicates that every member of a specified group or set satisfies a given condition or belongs entirely to another specified group.
-
E.
eligibleMembers
Indicates that certain entities meet the required criteria or conditions to be considered eligible members of a specified group or category.
- 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_69c008acbea48190991c6b834bb45d65 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0626d96ec8190816c00c44668177d |
completed | March 22, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c055fdea3c81908f5d910f0d36234a |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:20 p.m.