Triple
T24773106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walls, Shetland |
E619781
|
entity |
| Predicate | hasBayOrVoe |
P24183
|
FINISHED |
| Object | Walls Voe |
—
|
NE NERFINISHED |
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: Walls Voe | Statement: [Walls, Shetland, hasBayOrVoe, Walls Voe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBayOrVoe Context triple: [Walls, Shetland, hasBayOrVoe, Walls Voe]
-
A.
hasBayShape
Indicates that an entity possesses or exhibits a particular geometric or physical shape characteristic of a bay.
-
B.
hasNotableBay
chosen
Indicates that a place possesses a bay that is recognized for its significance, prominence, or special interest.
-
C.
hasVow
Indicates that one entity has made or is bound by a formal vow or promise in relation to another entity or context.
-
D.
hasBays
Indicates that something possesses or contains one or more bays, such as recessed areas, compartments, or harbor inlets.
-
E.
hasBayPlatforms
Indicates that a station or terminal is equipped with bay platforms, where tracks end in a dead-end configuration and trains enter and exit from the same direction.
- 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_69e2fabd04488190a2d13c97be745a2d |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410acff0481908b72047fe19d97de |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:32 a.m.