Triple
T592314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyannisport Club |
E17302
|
entity |
| Predicate | courseSetting |
P16025
|
FINISHED |
| Object | seaside links-style 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: seaside links-style course | Statement: [Hyannisport Club, courseSetting, seaside links-style course]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courseSetting Context triple: [Hyannisport Club, courseSetting, seaside links-style course]
-
A.
course
Indicates that an entity is an academic class or unit of instruction offered within an educational program.
-
B.
courseStructure
Indicates how a course is organized into its constituent parts, such as modules, units, lessons, and their sequencing or hierarchy.
-
C.
courseType
Indicates the classification or category of a course based on its nature, level, or instructional format.
-
D.
coreTeaching
Indicates that an entity serves as a primary or foundational teaching or instructional activity for another entity.
-
E.
typicalCourse
Indicates that one entity is a standard or commonly taken course associated with another entity, such as a program, curriculum, or field of study.
- 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_69a49379d09c8190ac7e00b24e2810b1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49bbaf53081908eed240bed09f63b |
completed | March 1, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69a494cd7d3c8190af008acf34a2293b |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a4985ada988190aaea628a9b55bca4 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:33 p.m.