Triple
T34611394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaylord Golf Mecca |
E888745
|
entity |
| Predicate | typeOfDestination |
P117281
|
FINISHED |
| Object | regional golf hub |
—
|
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: regional golf hub | Statement: [Gaylord Golf Mecca, typeOfDestination, regional golf hub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfDestination Context triple: [Gaylord Golf Mecca, typeOfDestination, regional golf hub]
-
A.
isTypeOfDestination
chosen
Indicates that one entity serves as a classification or category describing the kind or type of destination that another entity represents.
-
B.
transferDestinationType
Indicates the type or category of the destination entity to which something is being transferred.
-
C.
servesDestinationType
Indicates that an entity provides service to, or is intended for use with, a specific type or category of destination.
-
D.
isDestinationFor
Indicates that one entity serves as the endpoint or target location that another entity is intended to reach or be directed toward.
-
E.
isDestinationBased
Indicates that something is determined, organized, or classified according to its destination.
- 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_69f349d584e08190b40b9f6281ad50c4 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a01487b73488190954eb5143e6f246e |
completed | May 11, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_6a0145210ae481908da59b02efdbc397 |
completed | May 11, 2026, 2:55 a.m. |
Created at: May 1, 2026, 2:03 a.m.