Triple
T3673508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Golf Museum |
E77933
|
entity |
| Predicate | mainCollection |
P25033
|
FINISHED |
| Object | golf artifacts |
—
|
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: golf artifacts | Statement: [British Golf Museum, mainCollection, golf artifacts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCollection Context triple: [British Golf Museum, mainCollection, golf artifacts]
-
A.
collectionRepository
Indicates a relationship where a repository is responsible for storing, managing, or providing access to a collection.
-
B.
collectionScope
Indicates the extent, boundaries, or range over which a collection (such as a set of items, data, or resources) is defined or intended to apply.
-
C.
formerCollectionOf
Indicates that an entity once served as a collection or repository for another entity, but no longer holds that role.
-
D.
isMajorCollectionOf
chosen
Indicates that one entity serves as the primary or most significant collection or grouping of another entity.
-
E.
collects
Indicates that one entity gathers, accumulates, or brings together one or more other entities into its possession or control.
- 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_69ad85e083008190b2e1b7085fe500bd |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc45fbd1c819099023791452f1beb |
completed | March 8, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69adb84a20288190a092e4a1b045fe3f |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:25 p.m.