Triple
T19445846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ballaugh Bridge |
E486472
|
entity |
| Predicate | featureOfCourse |
P82715
|
FINISHED |
| Object | jump section |
—
|
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: jump section | Statement: [Ballaugh Bridge, featureOfCourse, jump section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featureOfCourse Context triple: [Ballaugh Bridge, featureOfCourse, jump section]
-
A.
courseIncludes
Indicates that a course contains or covers a particular component, such as a topic, module, lesson, or resource.
-
B.
hasCourseCharacteristic
chosen
Indicates that a course possesses or is associated with a particular characteristic, feature, or attribute.
-
C.
courseSetupCharacteristic
Indicates a defining setup-related property or configuration aspect associated with a course.
-
D.
notableCourse
Indicates that a course is particularly significant, distinguished, or noteworthy in relation to an entity (such as a person or institution).
-
E.
featuresInstitution
Indicates that one entity includes, presents, or highlights an institution as a notable component or participant.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6338a22608190bb31a1690ca0dab6 |
completed | April 20, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.