Triple
T16797606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glen Golf Club |
E408273
|
entity |
| Predicate | hasCourseEnvironment |
P13810
|
FINISHED |
| Object | links turf |
—
|
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: links turf | Statement: [Glen Golf Club, hasCourseEnvironment, links turf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCourseEnvironment Context triple: [Glen Golf Club, hasCourseEnvironment, links turf]
-
A.
hasTrainingEnvironment
Indicates that an entity is associated with, or operates within, a specific environment or setting used for training or practice.
-
B.
hasEnvironmentType
chosen
Indicates that an entity is associated with or occurs within a specific type or category of environment.
-
C.
hasApproachEnvironment
Indicates that an entity uses, is associated with, or is designed for a particular environment or context in which it operates or approaches something.
-
D.
hasHostCourse
Indicates that one entity serves as the primary or organizing course responsible for hosting or containing another related course or course component.
-
E.
hasStructureOnCourse
Indicates that a physical structure is located on, along, or directly associated with a specific course or route.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2ab08e8819097072a23c4a62392 |
completed | April 18, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.