Triple
T31118846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ynys Gored Goch |
E793166
|
entity |
| Predicate | navigationLandmarkFor |
P171340
|
FINISHED |
| Object | small craft on Menai Strait |
—
|
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: small craft on Menai Strait | Statement: [Ynys Gored Goch, navigationLandmarkFor, small craft on Menai Strait]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationLandmarkFor Context triple: [Ynys Gored Goch, navigationLandmarkFor, small craft on Menai Strait]
-
A.
mapLocation
Indicates a relationship where an entity is associated with a specific position or area on a map.
-
B.
navigationKnowledge
Indicates that an entity possesses information or understanding related to navigating or determining routes within an environment or system.
-
C.
proximityToLandmark
Indicates a spatial relationship where one entity is located near or close to a specified landmark.
-
D.
locationDirection
Indicates that one entity is located in a specific directional relation (such as north, south, above, or below) relative to another entity.
-
E.
typicalNearbyLandmarks
Indicates that certain landmarks are commonly found in the vicinity of a given place or location.
- 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69dfbf6ac8190ba2e6fc0adfd8b73 |
completed | May 3, 2026, 12:59 a.m. |
Created at: April 29, 2026, 9:04 p.m.