Triple
T7214598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montrose Links |
E149498
|
entity |
| Predicate | isLinksCourse |
P75475
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Montrose Links, isLinksCourse, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLinksCourse Context triple: [Montrose Links, isLinksCourse, true]
-
A.
usesCourse
Indicates that one entity makes use of, applies, or relies on a particular course in some context or activity.
-
B.
coursePar
Indicates that two entities (such as paths, lines, or trajectories) run alongside each other in the same general direction without intersecting.
-
C.
isTaughtAs
Indicates that something is presented or delivered as instructional content, typically within an educational or training context.
-
D.
notableCourse
Indicates that a course is particularly significant, distinguished, or noteworthy in relation to an entity (such as a person or institution).
-
E.
areTaughtIn
Indicates that certain subjects, courses, or topics are instructed or delivered within specific locations, classes, or educational settings.
- 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_69c687eca814819095abb52316b1af80 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e98cbebc8190941e76259c988790 |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e75f84e481909e7866186ae80cff |
completed | March 27, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69c6e889854481908c765ce2107f2d3a |
completed | March 27, 2026, 8:28 p.m. |
Created at: March 27, 2026, 2:53 p.m.