Triple
T29460479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wallace Collection |
E747220
|
entity |
| Predicate | coreCollectionDonor |
P167210
|
FINISHED |
| Object | Lady Wallace |
—
|
NE NERFINISHED |
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: Lady Wallace | Statement: [Wallace Collection, coreCollectionDonor, Lady Wallace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreCollectionDonor Context triple: [Wallace Collection, coreCollectionDonor, Lady Wallace]
-
A.
collectorSupport
Indicates that one entity provides assistance, resources, or backing to a collector in performing their collecting-related activities.
-
B.
collectionRepository
Indicates a relationship where a repository is responsible for storing, managing, or providing access to a collection.
-
C.
formerCollectionOf
Indicates that an entity once served as a collection or repository for another entity, but no longer holds that role.
-
D.
dedicatedCollectionTo
Indicates that a collection of items or works is formally assigned or devoted to a particular entity, purpose, or recipient.
-
E.
usesCollection
Indicates that one entity makes use of, depends on, or operates with a particular collection of items or resources.
- 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_69f0bd4125f88190b56104591351619c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66b703fb48190ad2b95cf523bdd00 |
completed | May 2, 2026, 9:24 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 28, 2026, 3:49 p.m.