Triple
T22290471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Canberra Golf Club |
E550979
|
entity |
| Predicate | courseGrassType |
P147946
|
FINISHED |
| Object | bentgrass greens |
—
|
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: bentgrass greens | Statement: [Royal Canberra Golf Club, courseGrassType, bentgrass greens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courseGrassType Context triple: [Royal Canberra Golf Club, courseGrassType, bentgrass greens]
-
A.
courseType
Indicates the classification or category of a course based on its nature, level, or instructional format.
-
B.
courseClass
Indicates that a particular course is classified as belonging to a specific academic class or category.
-
C.
courseShape
Indicates the geometric layout or configuration that defines the path or outline of a course.
-
D.
coursePar
Indicates that two entities (such as paths, lines, or trajectories) run alongside each other in the same general direction without intersecting.
-
E.
course
Indicates that an entity is an academic class or unit of instruction offered within an educational program.
- 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_69e11e45fb848190a1b2ae21296e3a5f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1560adde88190961d8fc24c1c4b3c |
completed | April 29, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e75dc7b08081909d64441e979c2fa4 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 16, 2026, 8:41 p.m.