Triple
T34550183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Course 1st tee |
E887039
|
entity |
| Predicate | courseHoleNumber |
P120558
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Old Course 1st tee, courseHoleNumber, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courseHoleNumber Context triple: [Old Course 1st tee, courseHoleNumber, 1]
-
A.
courseHole
Indicates that a particular hole is part of, or belongs to, a specific golf course.
-
B.
courseHoles
chosen
Indicates that a course consists of, or is associated with, a specified number or set of holes.
-
C.
numberOfHoles
Indicates the count of holes associated with or present in a given entity.
-
D.
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).
-
E.
hasNotableHolePar
Indicates that a particular hole on a golf course is especially significant or noteworthy for that player’s performance (e.g., key scoring or memorable play).
- 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_69f349cff89081908f91e0b064f4833e |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f72024a3348190b5e21ba600e64bb4 |
completed | May 3, 2026, 10:15 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:02 a.m.