Triple
T22801489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lagerstroemia loudonii |
E564404
|
entity |
| Predicate | hasGenusCommonName |
P78894
|
FINISHED |
| Object | crape myrtle |
—
|
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: crape myrtle | Statement: [Lagerstroemia loudonii, hasGenusCommonName, crape myrtle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGenusCommonName Context triple: [Lagerstroemia loudonii, hasGenusCommonName, crape myrtle]
-
A.
commonNameOfGenus
chosen
Indicates that the object is a commonly used name referring to the genus specified by the subject.
-
B.
hasGenus
Indicates that one entity belongs to, or is classified under, the biological genus represented by the other entity.
-
C.
includesSpeciesCommonName
Indicates that an entity contains or specifies the common (vernacular) name of a species.
-
D.
describedTaxonCommonName
Indicates that a taxon is being described or referenced using its common (vernacular) name rather than its scientific name.
-
E.
hasNamesakeGenus
Indicates that one entity serves as the namesake for a biological genus named after it.
- 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_69e2458185f88190b0045227ee420411 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17cdd87648190ba30f0b8f3ef7346 |
completed | April 29, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:31 p.m.