Triple
T36975504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lost City Golf Course |
E914684
|
entity |
| Predicate | 13th holePar |
P187238
|
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: [The Lost City Golf Course, 13th holePar, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 13th holePar Context triple: [The Lost City Golf Course, 13th holePar, 3]
-
A.
13th holeFeature
Indicates a feature or characteristic specifically associated with the 13th hole of a golf course.
-
B.
16thHolePar
Indicates that the par (expected number of strokes) is being specified for the 16th hole of a golf course.
-
C.
8thHolePar
Indicates that the par (expected number of strokes) is specified for the 8th hole of a golf course.
-
D.
16thHoleDescription
Indicates a descriptive relationship that specifies notable features, layout, or characteristics of the 16th hole in a course or sequence.
-
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. 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb34e4906c8190abb1c293fb84329a |
completed | May 6, 2026, 12:32 p.m. |
Created at: May 3, 2026, 4:14 p.m.