Triple
T21754139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Il ratto d’Europa |
E536991
|
entity |
| Predicate | ambientatoPresso |
P54861
|
FINISHED |
| Object | riva del mare |
—
|
LITERAL 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: riva del mare | Statement: [Il ratto d’Europa, ambientatoPresso, riva del mare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ambientatoPresso Context triple: [Il ratto d’Europa, ambientatoPresso, riva del mare]
-
A.
ambientSpace
Indicates the surrounding or containing space within which an object, structure, or geometric entity is situated or defined.
-
B.
around
Indicates that one entity is located or moves on all or most sides of another entity, encircling or surrounding it spatially.
-
C.
reservationLocatedAlong
Indicates that a reservation is situated along, adjacent to, or following the course or extent of a specified linear feature such as a road, river, or boundary.
-
D.
sometimesLocatedIn
Indicates that an entity is located in a given place only at certain times or under certain conditions, rather than permanently or always.
-
E.
portrayedInSetting
chosen
Indicates that an entity is depicted or represented within a particular setting, environment, or context.
- 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_69e0c46eab808190b848242d63a17c47 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01d8c57508190b45fb974ef0ded10 |
completed | April 28, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69e6969e46088190b13d6e9025775ea3 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:50 p.m.