Triple
T21808661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nothia aphylla |
E538413
|
entity |
| Predicate | specificEpithetMeaning |
P87618
|
FINISHED |
| Object | without leaves |
—
|
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: without leaves | Statement: [Nothia aphylla, specificEpithetMeaning, without leaves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specificEpithetMeaning Context triple: [Nothia aphylla, specificEpithetMeaning, without leaves]
-
A.
speciesNameMeaning
chosen
Indicates the meaning or etymological sense of a species’ scientific name.
-
B.
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.
-
C.
speciesDescription
Indicates a textual description that characterizes or explains the features, traits, or nature of a species.
-
D.
genusNameMeaning
Indicates the meaning or etymological sense of the name of a genus.
-
E.
speciesForm
Indicates that one entity is a specific biological form, variant, or manifestation of a species represented by another entity.
- 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_69e0c473f0f8819086c9d1b4a143bd67 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f078047ca88190a0efa4bc7f2faf80 |
completed | April 28, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69e6be815a108190be81d7c987d0c0d6 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:53 p.m.