Triple
T25003570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Touquet Golf Resort |
E625778
|
entity |
| Predicate | hasTournamentTypeHosted |
P150866
|
FINISHED |
| Object | amateur golf tournaments |
—
|
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: amateur golf tournaments | Statement: [Le Touquet Golf Resort, hasTournamentTypeHosted, amateur golf tournaments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTournamentTypeHosted Context triple: [Le Touquet Golf Resort, hasTournamentTypeHosted, amateur golf tournaments]
-
A.
hasTournamentType
chosen
Indicates that a tournament is classified as belonging to a specific type or category (e.g., league, knockout, friendly).
-
B.
hasTournament
Indicates that an entity organizes, hosts, or is associated with a specific tournament.
-
C.
hasHostedSport
Indicates that a place or organization has served as the venue or organizer for one or more sporting events.
-
D.
notableTournamentHosted
Indicates that an entity has served as the host or venue for a tournament considered notable or significant.
-
E.
tournamentHost
Indicates that one entity serves as the organizer or official host of a tournament involving the other entity.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 18, 2026, 6:05 a.m.