Triple
T20813902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dubai Desert Classic |
E512384
|
entity |
| Predicate | hasCutAfter |
P25030
|
FINISHED |
| Object | 36 holes |
—
|
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: 36 holes | Statement: [Dubai Desert Classic, hasCutAfter, 36 holes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCutAfter Context triple: [Dubai Desert Classic, hasCutAfter, 36 holes]
-
A.
hasCut
Indicates that one entity has made or possesses a cut in, on, or through another entity.
-
B.
hasCutAfterRound
chosen
Indicates that an entity is eliminated or removed from participation after a specified round.
-
C.
hasTypicalCut
Indicates that one entity is characterized by or associated with a standard or typical type of cut of another entity.
-
D.
isCutInto
Indicates that one entity is divided or separated into pieces or segments that become the other entity.
-
E.
hasSubsequent
Indicates that one entity occurs, appears, or is positioned after another in a defined sequence or order.
- 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_69e0b4cd25088190b48ca9700cd24efc |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2d4e43c8190aecce82a3f7e2de0 |
completed | April 21, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:40 p.m.