Triple
T21487046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lock |
E530141
|
entity |
| Predicate | hasCollectionHistory |
P56448
|
FINISHED |
| Object | sold at auction multiple times |
—
|
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: sold at auction multiple times | Statement: [The Lock, hasCollectionHistory, sold at auction multiple times]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollectionHistory Context triple: [The Lock, hasCollectionHistory, sold at auction multiple times]
-
A.
hasHistoryIn
Indicates that an entity has a past involvement, presence, or record of activity within a particular domain, context, or location.
-
B.
collectionHistory
chosen
Indicates the record of when, how, and from whom an item or set of items was acquired, transferred, or otherwise added to a collection over time.
-
C.
hasResourceHistory
Indicates that an entity is associated with a record or sequence of past states, usages, or changes of a particular resource over time.
-
D.
hasTypeHistory
Indicates that an entity is associated with a record or sequence of its past and present types or classifications over time.
-
E.
hasHistorySince
Indicates that an entity has maintained a particular state, condition, or relationship continuously starting from a specified point in time.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea37e25c81909ae185fcab19bc4b |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:22 p.m.