Triple
T5330566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birsay |
E123294
|
entity |
| Predicate | accessToBroughOfBirsay |
P62863
|
FINISHED |
| Object | tidal causeway at low tide |
—
|
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: tidal causeway at low tide | Statement: [Birsay, accessToBroughOfBirsay, tidal causeway at low tide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessToBroughOfBirsay Context triple: [Birsay, accessToBroughOfBirsay, tidal causeway at low tide]
-
A.
tourAccess
Indicates that an entity is permitted to participate in, enter, or make use of a specific tour.
-
B.
hasLandmarkAtEntrance
Indicates that a specific landmark is located at or directly adjacent to the entrance of something.
-
C.
touristAccess
Indicates that a place or resource is available for use or visitation by tourists.
-
D.
hasLoch
Indicates that one entity possesses, contains, or features a loch (lake or sea inlet) as part of its characteristics or composition.
-
E.
guardedEntranceTo
Indicates that one entity serves as a protective or controlling barrier for access to another entity’s entrance.
- 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_69bd46477f9081909d242a327d749466 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85969cc88190a3a5efbab7d9fe86 |
completed | March 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69bd84583dbc819088a03e3afb30178c |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd8501d53c81908371bd5195ba5703 |
completed | March 20, 2026, 5:33 p.m. |
Created at: March 20, 2026, 2 p.m.