Triple
T6838581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Troon Golf Club |
E157512
|
entity |
| Predicate | 8thHolePar |
P73453
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Royal Troon Golf Club, 8thHolePar, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 8thHolePar Context triple: [Royal Troon Golf Club, 8thHolePar, 3]
-
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.
notableHole
Indicates that an entity has a hole or opening that is significant or noteworthy in some context.
-
C.
typicalCoursePar
Indicates that one course is a typical or standard parallel (i.e., alternative but equivalent) course to another within a curriculum or program.
-
D.
hasYardage
Indicates that something possesses or is associated with a specific measured distance or length, typically expressed in yards.
-
E.
hasWaterHazards
Indicates that the subject contains or is associated with one or more water-based obstacles or danger areas.
- F. None of above. chosen
Provenance (4 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d67ee1c88190b82a9b6b3d1e3875 |
completed | March 27, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c6d09f90648190bc0a462c7d59de1b |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d623aba88190a93ec9c83508c960 |
completed | March 27, 2026, 7:10 p.m. |
Created at: March 27, 2026, 2:19 p.m.