Triple
T22910681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lahinch Golf Club (redesign) |
E568580
|
entity |
| Predicate | hasCourseLayout |
P150209
|
FINISHED |
| Object | 18-hole layout |
—
|
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: 18-hole layout | Statement: [Lahinch Golf Club (redesign), hasCourseLayout, 18-hole layout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCourseLayout Context triple: [Lahinch Golf Club (redesign), hasCourseLayout, 18-hole layout]
-
A.
hasStructureOnCourse
Indicates that a physical structure is located on, along, or directly associated with a specific course or route.
-
B.
hasCoursePattern
Indicates that an entity follows, is associated with, or is defined by a particular course structure or pattern.
-
C.
hasCurricularStructure
Indicates that an educational program or course is organized according to a defined curricular framework or structure.
-
D.
hasCurriculumBasis
Indicates that one entity’s curriculum is founded on, derived from, or guided by another entity as its basis.
-
E.
hasCourseOrientation
Indicates that a course is associated with a particular orientation, such as its introductory session, onboarding format, or general directional focus.
- 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_69e2458cd9e48190943ad2e34485d939 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1807493a881909e7ee6e8c4c5d4ad |
completed | April 29, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:42 p.m.