Triple
T28855432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pedaliaceae |
E728720
|
entity |
| Predicate | hasMemberWithCommonUse |
P153407
|
FINISHED |
| Object | sesame seed production |
—
|
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: sesame seed production | Statement: [Pedaliaceae, hasMemberWithCommonUse, sesame seed production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemberWithCommonUse Context triple: [Pedaliaceae, hasMemberWithCommonUse, sesame seed production]
-
A.
hasMemberAlsoIn
Indicates that an entity has at least one member who also belongs to another specified group or collection.
-
B.
hasMembersWith
chosen
Indicates that a group or collection includes one or more specific members that satisfy a given condition or characteristic.
-
C.
hasHumanUse
Indicates that something is used, employed, or utilized by humans for a particular purpose or benefit.
-
D.
hasCoreMember
Indicates that an entity includes another entity as a central or primary member of its group, organization, or structure.
-
E.
containsUse
Indicates that one entity includes or makes use of another entity as part of its composition, function, or implementation.
- 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: April 28, 2026, 6:45 a.m.