Triple
T22910178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eisenhower Tree |
E568566
|
entity |
| Predicate | courseHolePar |
P113132
|
FINISHED |
| Object | par 4 (17th hole) |
—
|
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: par 4 (17th hole) | Statement: [Eisenhower Tree, courseHolePar, par 4 (17th hole)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courseHolePar Context triple: [Eisenhower Tree, courseHolePar, par 4 (17th hole)]
-
A.
golfCoursePar
chosen
Indicates the standard number of strokes a skilled golfer is expected to take to complete a particular golf course or hole.
-
B.
8thHolePar
Indicates that the par (expected number of strokes) is specified for the 8th hole of a golf course.
-
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.
courseHole
Indicates that a particular hole is part of, or belongs to, a specific golf course.
-
E.
notableHole
Indicates that an entity has a hole or opening that is significant or noteworthy in some context.
- 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_69e2458cd9e48190943ad2e34485d939 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1807350008190a057e8fb5c363c5f |
completed | April 29, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69ef3b6b2e2481908258156937b5a745 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:42 p.m.