Triple
T30011597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Botanic Garden of Belgium |
E762475
|
entity |
| Predicate | hasHerbariumSize |
P184380
|
FINISHED |
| Object | one of the largest herbaria in Europe |
—
|
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: one of the largest herbaria in Europe | Statement: [National Botanic Garden of Belgium, hasHerbariumSize, one of the largest herbaria in Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHerbariumSize Context triple: [National Botanic Garden of Belgium, hasHerbariumSize, one of the largest herbaria in Europe]
-
A.
hasHerbarium
Indicates that an entity possesses, is associated with, or maintains a herbarium collection.
-
B.
hasNumberOfPlantCollections
Indicates the quantity of distinct plant collections associated with an entity.
-
C.
hasHerbariumCode
Indicates that an institution or collection is associated with a specific standardized herbarium code used to identify it.
-
D.
areaOfBotanicalCollection
Indicates the total surface area occupied by a botanical collection.
-
E.
hasBotanicalGardenArea_ha
Indicates that an entity possesses a botanical garden whose area is measured in hectares.
- 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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7b0e3917481908a394680d76743c3 |
completed | May 3, 2026, 8:32 p.m. |
Created at: April 29, 2026, 6:44 p.m.