Triple
T35943111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La spiaggia |
E1039505
|
entity |
| Predicate | hasScreenLocation |
P193802
|
FINISHED |
| Object | Italian seaside resort |
—
|
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: Italian seaside resort | Statement: [La spiaggia, hasScreenLocation, Italian seaside resort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScreenLocation Context triple: [La spiaggia, hasScreenLocation, Italian seaside resort]
-
A.
hasOnScreenLocationType
Indicates that an entity’s location, as presented or visible on a screen, is of a specified type or category.
-
B.
hasOnScreenRelative
Indicates that one entity has a family member who appears or is depicted on screen in relation to it.
-
C.
hasScreen
Indicates that an entity is equipped with or includes a screen or display component.
-
D.
hasSceneLocation
Indicates that a scene or event takes place at, or is set in, a specific location.
-
E.
hasLocationComponent
Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
- F. None of above. chosen
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_69f76e24bbd0819096b837d35371639a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
| PDg | Predicate description generation | batch_69fd553c01488190b9fda48b4a728f04 |
completed | May 8, 2026, 3:15 a.m. |
Created at: May 3, 2026, 4:07 p.m.