Triple
T14435996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dirachma somalensis |
E357961
|
entity |
| Predicate | genusSize |
P114266
|
FINISHED |
| Object | one of two known species in genus Dirachma |
—
|
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: one of two known species in genus Dirachma | Statement: [Dirachma somalensis, genusSize, one of two known species in genus Dirachma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genusSize Context triple: [Dirachma somalensis, genusSize, one of two known species in genus Dirachma]
-
A.
numberOfGenera
Indicates the total count of genera associated with or contained within a given entity.
-
B.
hasGenus
Indicates that one entity belongs to, or is classified under, the biological genus represented by the other entity.
-
C.
genusIncludes
Indicates that a particular genus contains or encompasses the specified subordinate taxonomic entities (such as species or subspecies).
-
D.
genusCharacteristic
Indicates that a particular characteristic or trait is typical of, or defining for, a given genus.
-
E.
speciesNumber
Indicates the numerical identifier or count associated with a particular species in a given context.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9148cf4481909082cc91b2f76218 |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:18 a.m.