Triple
T19693417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doral Open |
E472891
|
entity |
| Predicate | typicalWinningScoreRelationToPar |
P26150
|
FINISHED |
| Object | under par |
—
|
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: under par | Statement: [Doral Open, typicalWinningScoreRelationToPar, under par]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalWinningScoreRelationToPar Context triple: [Doral Open, typicalWinningScoreRelationToPar, under par]
-
A.
typicalWinningScoreRelativeToPar
chosen
Indicates the usual or expected winning score in relation to the course’s par (e.g., how many strokes under or over par typically wins).
-
B.
typicalCoursePar
Indicates that one course is a typical or standard parallel (i.e., alternative but equivalent) course to another within a curriculum or program.
-
C.
golfCoursePar
Indicates the standard number of strokes a skilled golfer is expected to take to complete a particular golf course or hole.
-
D.
8thHolePar
Indicates that the par (expected number of strokes) is specified for the 8th hole of a golf course.
-
E.
gameWinningScoreBy
Indicates that a particular score is the decisive amount by which a game is won by an 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e64211e5d481908358d922e0dca271 |
completed | April 20, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.