Triple
T4331966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glasgow–Barra beach landing route |
E96772
|
entity |
| Predicate | schedulingConstraint |
P46295
|
FINISHED |
| Object | tide-dependent operations at Barra |
—
|
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: tide-dependent operations at Barra | Statement: [Glasgow–Barra beach landing route, schedulingConstraint, tide-dependent operations at Barra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: schedulingConstraint Context triple: [Glasgow–Barra beach landing route, schedulingConstraint, tide-dependent operations at Barra]
-
A.
schedulingRule
chosen
Indicates a rule or constraint that governs when, how, or under what conditions an event or task may be scheduled.
-
B.
constrainedBy
Indicates that one entity’s state, behavior, or possibilities are limited, restricted, or governed by another entity.
-
C.
designedToConstrain
Indicates that one entity is intentionally created or configured to limit, restrict, or control the behavior, range, or properties of another entity.
-
D.
usedForScheduling
Indicates that something is employed to plan, arrange, or coordinate the timing of events, tasks, or activities.
-
E.
scheduledAs
Indicates that one entity is assigned or arranged to occur or function in the role, time, or capacity specified by another entity within a schedule.
- 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_69b34542fd908190b11b08faad8decfd |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3514dc588819086a4c6d585c1b5b1 |
completed | March 12, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69b34f4e13fc8190a42c519f37959d27 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:13 p.m.