Triple
T17597132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Octoknemaceae |
E428601
|
entity |
| Predicate | hasScientificNameEnding |
P103831
|
FINISHED |
| Object | -aceae |
—
|
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: -aceae | Statement: [Octoknemaceae, hasScientificNameEnding, -aceae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScientificNameEnding Context triple: [Octoknemaceae, hasScientificNameEnding, -aceae]
-
A.
nameEnding
chosen
Indicates that one entity’s name ends with the string or substring represented by the other entity.
-
B.
binomialName
Indicates the formal scientific name assigned to a species, typically composed of its genus and specific epithet.
-
C.
specificEpithet
Indicates the taxonomic relationship where a specific epithet designates the species-level name within a binomial scientific name, distinguishing one species from others in the same genus.
-
D.
hasNounEnding
Indicates that something possesses or exhibits a particular noun-forming ending or suffix.
-
E.
hasScientificSpecies
Indicates that an entity is associated with a specific scientific (Latin) species name.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e469ec335c8190abcaff700cfff23b |
completed | April 19, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:51 a.m.