Triple
T14293150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valle de Bravo |
E354366
|
entity |
| Predicate | isWeekendRetreatFor |
P71063
|
FINISHED |
| Object | residents of Mexico City |
—
|
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: residents of Mexico City | Statement: [Valle de Bravo, isWeekendRetreatFor, residents of Mexico City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWeekendRetreatFor Context triple: [Valle de Bravo, isWeekendRetreatFor, residents of Mexico City]
-
A.
retreatType
Indicates the specific kind or category of retreat associated with an event, action, or entity.
-
B.
retreatSeason
Indicates the time of year during which a retreat customarily takes place or is scheduled.
-
C.
isResortDestinationFor
chosen
Indicates that a place serves as a resort destination specifically intended for or frequented by a particular person, group, or entity.
-
D.
isResortTown
Indicates that a town functions primarily as a resort destination, typically focused on tourism, leisure, and vacation activities.
-
E.
hasRecreationPurpose
Indicates that something is used or intended to be used for recreational or leisure activities.
- 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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de7179368081908117a9ccfbf94fd4 |
completed | April 14, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:11 a.m.