Triple
T26848197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Norma |
E675981
|
entity |
| Predicate | hasResortStyle |
P141936
|
FINISHED |
| Object | compact village |
—
|
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: compact village | Statement: [La Norma, hasResortStyle, compact village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResortStyle Context triple: [La Norma, hasResortStyle, compact village]
-
A.
hasResortType
Indicates that an entity (such as a resort or accommodation) is associated with a specific category or type of resort (e.g., beach resort, ski resort, spa resort).
-
B.
hasResortHotel
Indicates that one entity owns, includes, or is associated with a resort hotel as part of its facilities or offerings.
-
C.
hasResortBrand
Indicates that a resort is associated with, operated by, or marketed under a specific resort brand.
-
D.
hasResortCharacter
chosen
Indicates that something possesses qualities or features characteristic of a resort, such as leisure-oriented amenities or a vacation-like atmosphere.
-
E.
hasTourismStyle
Indicates the type or style of tourism associated with or characteristic of a particular entity.
- 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_69eee9b8d5e88190a07d3455c0fbb21f |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69fe189fec148190aeef51b417ba15b0 |
completed | May 8, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69fe17285b0881908de7569d8dbd20bd |
completed | May 8, 2026, 5:02 p.m. |
Created at: April 27, 2026, 5:14 a.m.