Triple
T10713840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zihuatanejo |
E252608
|
entity |
| Predicate | tourismDevelopmentStyle |
P82318
|
FINISHED |
| Object | more traditional than Ixtapa |
—
|
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: more traditional than Ixtapa | Statement: [Zihuatanejo, tourismDevelopmentStyle, more traditional than Ixtapa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourismDevelopmentStyle Context triple: [Zihuatanejo, tourismDevelopmentStyle, more traditional than Ixtapa]
-
A.
hasTourismStyle
chosen
Indicates the type or style of tourism associated with or characteristic of a particular entity.
-
B.
tourismTheme
Indicates the main subject or focus of a tourism-related activity, service, or destination (such as cultural, adventure, or eco-tourism).
-
C.
tourismType
Indicates the specific category or kind of tourism activity or experience associated with an entity.
-
D.
tourismDevelopmentLevel
Indicates the extent or intensity to which tourism-related infrastructure, services, and activities have been developed in a given area.
-
E.
urbanPlanningStyle
Indicates the characteristic approach or methodology used in planning and organizing urban spaces and development.
- 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_69d6aa5cbabc8190973e683950d89faf |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fe54465081909640f6d7a2314fcb |
completed | April 9, 2026, 1:18 a.m. |
| PD | Predicate disambiguation | batch_69d6f30455888190b77f476b8418eaee |
completed | April 9, 2026, 12:29 a.m. |
Created at: April 8, 2026, 9:13 p.m.