Triple
T26857890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Plan-de-la-Tour |
E676243
|
entity |
| Predicate | nearestLargeResort |
P42027
|
FINISHED |
| Object | Saint-Tropez |
—
|
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: Saint-Tropez | Statement: [Le Plan-de-la-Tour, nearestLargeResort, Saint-Tropez]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestLargeResort Context triple: [Le Plan-de-la-Tour, nearestLargeResort, Saint-Tropez]
-
A.
nearbyResortSection
Indicates that one resort section is located close to another resort section in physical proximity.
-
B.
nearbyResortArea
chosen
Indicates that a resort area is located close to or within a short distance of a specified place or entity.
-
C.
associatedResort
Indicates a relationship where one entity is linked or connected to a specific resort, typically as its related or corresponding resort.
-
D.
isResortOf
Indicates that a location or facility functions as a resort associated with, belonging to, or serving a particular entity (such as a city, region, or organization).
-
E.
resort
Indicates that one entity is used or turned to as a final or alternative option by another entity, often after other possibilities have been exhausted.
- 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_69eee9b9d7708190a15d7485709ae981 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 5:22 a.m.