Triple
T18908106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Museum herbarium |
E462520
|
entity |
| Predicate | enrichedBy |
P5633
|
FINISHED |
| Object | Robert Brown's collections |
—
|
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: Robert Brown's collections | Statement: [British Museum herbarium, enrichedBy, Robert Brown's collections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enrichedBy Context triple: [British Museum herbarium, enrichedBy, Robert Brown's collections]
-
A.
enhancedBy
Indicates that one entity’s value, effectiveness, or impact is increased or improved as a result of another entity.
-
B.
enrichesMaterial
Indicates that one entity improves or enhances the quality, properties, or value of a material.
-
C.
expandedBy
chosen
Indicates that one entity increases, elaborates, or builds upon the scope, detail, or extent of another entity.
-
D.
richIn
Indicates that something contains a high amount or concentration of a particular substance, quality, or resource.
-
E.
hasRich
Indicates that an entity possesses or is characterized by a high level of wealth, abundance, or valuable resources.
- 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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c52eed1881908929dace845ae008 |
completed | April 20, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.