Triple
T36628075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isleworth Mona Lisa |
E904229
|
entity |
| Predicate | hasProponents |
P9868
|
FINISHED |
| Object | Mona Lisa Foundation |
E2192559
|
NE 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: Mona Lisa Foundation | Statement: [Isleworth Mona Lisa, hasProponents, Mona Lisa Foundation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProponents Context triple: [Isleworth Mona Lisa, hasProponents, Mona Lisa Foundation]
-
A.
hasSupportersIn
Indicates that an entity is backed or endorsed by people or groups located within a specified place or region.
-
B.
hasMainProponent
Indicates that one entity is the primary advocate, champion, or leading supporter of another entity.
-
C.
hasLaterProponent
Indicates that an idea, theory, or position was subsequently supported or advocated by a later individual or group.
-
D.
hasHistoricalProponent
chosen
Indicates that an entity has been advocated, supported, or promoted by a specific person or group in the past.
-
E.
hasProposal
Indicates that an entity possesses, is associated with, or is the subject of a specific proposal.
- F. None of above.
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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3a381293248190974e06b1acc75e9d |
completed | June 23, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.