Triple
T28729496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giovanni Antonio Canal |
E730617
|
entity |
| Predicate | worksHeldIn |
P149220
|
FINISHED |
| Object | National Gallery, London |
—
|
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: National Gallery, London | Statement: [Giovanni Antonio Canal, worksHeldIn, National Gallery, London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksHeldIn Context triple: [Giovanni Antonio Canal, worksHeldIn, National Gallery, London]
-
A.
significantWorkHeld
chosen
Indicates that an entity possesses, houses, or maintains an important or notable work (such as an artwork, document, or creation) in its collection or custody.
-
B.
workRepresented
Indicates that one entity is a representation (such as a depiction, adaptation, or portrayal) of another work.
-
C.
workedAs
Indicates that an entity held a particular job, role, or position, performing work in that capacity.
-
D.
worksFrom
Indicates that an entity performs its work or duties starting from or based at a specified location or source.
-
E.
workTypeContributedTo
Indicates that an entity contributed to the creation, development, or production of a particular type of work.
- 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_69f043eae0908190b28ce314686247d7 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 28, 2026, 5:57 a.m.