Triple
T17739275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Coulter |
E442808
|
entity |
| Predicate | hasCollected |
P88587
|
FINISHED |
| Object | plant specimens |
—
|
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: plant specimens | Statement: [Thomas Coulter, hasCollected, plant specimens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollected Context triple: [Thomas Coulter, hasCollected, plant specimens]
-
A.
hasCollector
chosen
Indicates that an entity is associated with, or owned/curated by, a specific collector.
-
B.
hasProperCollect
Indicates that an entity is associated with a specific proper collect, i.e., a designated formal prayer or liturgical text assigned to it.
-
C.
hasCollectedEdition
Indicates that one entity possesses or maintains a special or curated edition or version of another entity as part of a collection.
-
D.
hasCollection
Indicates that an entity possesses, maintains, or is associated with a set or group of related items treated as a collection.
-
E.
hasCollectionFrom
Indicates that an entity possesses or maintains a collection that originates from, or is sourced from, another specified entity.
- 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47acb05848190a4b7edb98f15b8c6 |
completed | April 19, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:09 a.m.