Triple
T36667416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carnoustie Golf Links |
E905303
|
entity |
| Predicate | hasFamousIncident |
P18677
|
FINISHED |
| Object | Jean Van de Velde collapse at 18th hole in 1999 Open |
—
|
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: Jean Van de Velde collapse at 18th hole in 1999 Open | Statement: [Carnoustie Golf Links, hasFamousIncident, Jean Van de Velde collapse at 18th hole in 1999 Open]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamousIncident Context triple: [Carnoustie Golf Links, hasFamousIncident, Jean Van de Velde collapse at 18th hole in 1999 Open]
-
A.
hasNamesakeNotableEvent
Indicates that one entity serves as the namesake for a notable event associated with the other entity.
-
B.
notableIncidentType
Indicates the specific category or kind of significant event or incident associated with an entity.
-
C.
hasNotableIncident
chosen
Indicates that an entity is associated with a significant or noteworthy event, occurrence, or incident.
-
D.
significantEventInvolves
Indicates that a significant event includes or engages a particular entity as a participant or key element.
-
E.
famousForEvent
Indicates that an entity is widely known or recognized specifically because of a particular event.
- 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_69f76e6f10008190aea41746aa1b186e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe779248c081909f0ed1a2a0df23db |
completed | May 8, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69fe76eaf6d48190998bc7168749cc42 |
completed | May 8, 2026, 11:51 p.m. |
Created at: May 3, 2026, 4:12 p.m.