Triple
T25676056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L.B. Houston Golf Course |
E643807
|
entity |
| Predicate | isTypeOfCourse |
P7752
|
FINISHED |
| Object | regulation course |
—
|
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: regulation course | Statement: [L.B. Houston Golf Course, isTypeOfCourse, regulation course]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTypeOfCourse Context triple: [L.B. Houston Golf Course, isTypeOfCourse, regulation course]
-
A.
isCourse
Indicates that an entity functions as or qualifies as a course within a given context or system.
-
B.
courseType
chosen
Indicates the classification or category of a course based on its nature, level, or instructional format.
-
C.
isAdditionalCourseOf
Indicates that one course serves as an extra or supplementary course in relation to another primary course.
-
D.
isLinksCourse
Indicates that one course is linked or associated with another course in a meaningful way (such as being related, connected, or part of the same learning path).
-
E.
offersCourseType
Indicates that an entity provides or makes available a course of a specified type.
- 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_69e77e7f69808190ad27df1006f6037a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 21, 2026, 7:38 p.m.