Triple
T23038377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Mid-Amateur |
E573670
|
entity |
| Predicate | numberOfHolesStrokePlayQualifying |
P8596
|
FINISHED |
| Object | 36 |
—
|
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 | Statement: [U.S. Mid-Amateur, numberOfHolesStrokePlayQualifying, 36]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfHolesStrokePlayQualifying Context triple: [U.S. Mid-Amateur, numberOfHolesStrokePlayQualifying, 36]
-
A.
typicalWinningScoreRelativeToPar
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.
estimatedHolesInOne
Indicates that a numerical estimate is being made of how many holes-in-one (aces) are expected to occur in a given golf context (such as for a player, round, event, or time period).
-
C.
golfCoursePar
Indicates the standard number of strokes a skilled golfer is expected to take to complete a particular golf course or hole.
-
D.
numberOfHoles
chosen
Indicates the count of holes associated with or present in a given entity.
-
E.
hasWaterHazards
Indicates that the subject contains or is associated with one or more water-based obstacles or danger areas.
- 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_69e245b911188190bc3d96326c847969 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f185111f0881908991fcd6cdc7db9f |
completed | April 29, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69ef3ba004a48190885aece88efd1f52 |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:53 p.m.