Triple
T22185860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magnus von Lagerström |
E548294
|
entity |
| Predicate | hasNameInBotanicalLatin |
P3646
|
FINISHED |
| Object | Lagerstroemius |
—
|
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: Lagerstroemius | Statement: [Magnus von Lagerström, hasNameInBotanicalLatin, Lagerstroemius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameInBotanicalLatin Context triple: [Magnus von Lagerström, hasNameInBotanicalLatin, Lagerstroemius]
-
A.
hasLatinName
chosen
Indicates that an entity is associated with a specific Latin (scientific) name.
-
B.
hasLatinNameMeaning
Indicates that an entity’s Latin name conveys a specific meaning or refers to a particular concept.
-
C.
isBotanical
Indicates that something pertains to plants or plant science, such as being derived from, related to, or characteristic of botanical life or botany.
-
D.
hasOfficialNameInLatin
Indicates that an entity has an official or formally recognized name expressed in the Latin language.
-
E.
ortoBotanicoInstanceOf
Indicates that something is classified as an instance of an Orto Botanico (a specific botanical garden).
- 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_69e11e3e0c7c8190b30d278845e2497e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12aa8f178819094d1556df5aee5b9 |
completed | April 28, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:35 p.m.