Triple
T9670853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alfred Dunhill Cup |
E234021
|
entity |
| Predicate | notableVenueCharacteristic |
P46334
|
FINISHED |
| Object | historic links course |
—
|
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: historic links course | Statement: [Alfred Dunhill Cup, notableVenueCharacteristic, historic links course]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableVenueCharacteristic Context triple: [Alfred Dunhill Cup, notableVenueCharacteristic, historic links course]
-
A.
tourismCharacteristic
Indicates that something has a specific feature, quality, or attribute relevant to tourism, such as what makes a place, service, or activity notable or suitable for tourists.
-
B.
notableLocationFeature
chosen
Indicates that a location is characterized or distinguished by a particular notable physical or contextual feature.
-
C.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
-
D.
typicalVenues
Indicates that the specified locations are common or standard places where the associated activity, event, or entity usually occurs or is hosted.
-
E.
notableRecordingVenueFor
Indicates that a venue is particularly recognized or distinguished as the place where a specific recording was made.
- 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_69ca848f55e48190b3f67252571c3d45 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c6949108190b699442e5c2aacf9 |
completed | April 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b5d40c8190850ad7a351445f32 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:15 p.m.