Triple
T31948808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Story of San Michele |
E815723
|
entity |
| Predicate | notablePlaceDescribed |
P42538
|
FINISHED |
| Object | Villa San Michele, Capri |
E234551
|
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: Villa San Michele, Capri | Statement: [The Story of San Michele, notablePlaceDescribed, Villa San Michele, Capri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePlaceDescribed Context triple: [The Story of San Michele, notablePlaceDescribed, Villa San Michele, Capri]
-
A.
notablePlaceDepicted
Indicates that a work (such as an image, artwork, or media) prominently depicts a place that is considered notable or significant.
-
B.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
-
C.
notableLocation
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
-
D.
placeDescribed
chosen
Indicates that one entity provides a description or account of a particular place or location.
-
E.
notableLocationOn
Indicates that a particular location is especially significant or noteworthy in relation to a specified entity or context.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2eb13e62708190a55796ba1f665c89 |
completed | June 14, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:07 a.m.