Triple
T34946824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lansdowne collection |
E1007876
|
entity |
| Predicate | hasCollectionStatus |
P206747
|
FINISHED |
| Object | private collection |
—
|
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: private collection | Statement: [Lansdowne collection, hasCollectionStatus, private collection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollectionStatus Context triple: [Lansdowne collection, hasCollectionStatus, private collection]
-
A.
hasCollectorStatus
Indicates that an entity holds a specific collector-related status or designation in relation to another entity or context.
-
B.
hasCollection
Indicates that an entity possesses, maintains, or is associated with a set or group of related items treated as a collection.
-
C.
collectingStatus
Indicates the current state or phase of an ongoing collection process or activity.
-
D.
hasCollectionDisplay
Indicates that an entity is presented or made visible as part of a collection display, such as in an exhibition or grouped showcase.
-
E.
hasGroupStatus
Indicates that an entity possesses a particular status, role, or condition within a group or collective context.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4 p.m.