Triple
T28080687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Harbor of Gloucester (Metropolitan Museum of Art painting) |
E709666
|
entity |
| Predicate | stateOfMuseum |
P37091
|
FINISHED |
| Object | New York |
—
|
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: New York | Statement: [The Harbor of Gloucester (Metropolitan Museum of Art painting), stateOfMuseum, New York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateOfMuseum Context triple: [The Harbor of Gloucester (Metropolitan Museum of Art painting), stateOfMuseum, New York]
-
A.
museumHolds
Indicates that a museum possesses, preserves, or has custody of a particular item or collection within its holdings.
-
B.
museumAt
Indicates that an entity (such as an exhibit, artifact, or event) is located at or associated with a particular museum.
-
C.
hasMuseumAt
chosen
Indicates that a museum is located at or exists in a specified place or location.
-
D.
hasMuseumFunction
Indicates that an entity serves the role or performs the function of a museum.
-
E.
isRegionalMuseum
Indicates that a museum operates at a regional level, serving and representing a specific geographic area rather than a local, national, or international scope.
- 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_69ef9b7037f0819095bb90eaccbcaf32 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 27, 2026, 8:51 p.m.