Triple
T10291049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Cobá |
E241363
|
entity |
| Predicate | hasNearbyService |
P88772
|
FINISHED |
| Object | local guides at Cobá |
—
|
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: local guides at Cobá | Statement: [Lake Cobá, hasNearbyService, local guides at Cobá]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyService Context triple: [Lake Cobá, hasNearbyService, local guides at Cobá]
-
A.
hasNearbyFunction
Indicates that one entity has another entity located close by that serves a related or supportive function.
-
B.
hasNearbyMode
Indicates that one entity has another entity located close enough to be considered in its immediate vicinity or surrounding area.
-
C.
hasOpenSpaceNearby
Indicates that an entity is located near or adjacent to an area that is open, unobstructed, or undeveloped.
-
D.
hasNearbyInstallation
chosen
Indicates that one entity has another installation or facility located close to it in physical space.
-
E.
hasNearbyEventType
Indicates that an event of a specified type occurs in close spatial or contextual proximity to a given reference entity or location.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f117708190928f92ae2611d724 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:41 a.m.