Triple
T10479789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laurentii Salvii |
E247139
|
entity |
| Predicate | roleInBotany |
P94256
|
FINISHED |
| Object | publisher of foundational botanical works |
—
|
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: publisher of foundational botanical works | Statement: [Laurentii Salvii, roleInBotany, publisher of foundational botanical works]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInBotany Context triple: [Laurentii Salvii, roleInBotany, publisher of foundational botanical works]
-
A.
isBotanical
Indicates that something pertains to plants or plant science, such as being derived from, related to, or characteristic of botanical life or botany.
-
B.
plant
Indicates that an entity places or sets something firmly in or on a location, often so it will grow, remain fixed, or be established there.
-
C.
plantKingdom
Indicates that the subject belongs to, or is classified within, the plant kingdom.
-
D.
plantType
Indicates the specific kind or category of plant that an entity is classified as.
-
E.
involvesPlant
Indicates that the relationship or action includes or pertains to a plant as a participating entity.
- 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5095b2ec881909e1220d83e750a75 |
completed | April 7, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d4fb84bafc8190819757b93620508a |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe058fcc81909428137d9ffd6d90 |
completed | April 7, 2026, 12:52 p.m. |
Created at: April 6, 2026, 12:22 p.m.