Triple
T26898973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port St Mary Harbour |
E677972
|
entity |
| Predicate | hasNavigationMark |
P47583
|
FINISHED |
| Object | harbour lights |
—
|
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: harbour lights | Statement: [Port St Mary Harbour, hasNavigationMark, harbour lights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNavigationMark Context triple: [Port St Mary Harbour, hasNavigationMark, harbour lights]
-
A.
hasNavigationStatus
Indicates the current state or condition of an entity’s navigation, such as whether and how it is actively navigating.
-
B.
hasNavigationCharacteristic
chosen
Indicates that an entity possesses a specific property, feature, or quality related to navigation or navigational behavior.
-
C.
hasNavigationKey
Indicates that one entity serves as a navigation key or reference used to access, locate, or traverse to another related entity.
-
D.
hasNavigationSpan
Indicates that one entity includes or is associated with a specific navigational range or segment used for movement or routing.
-
E.
hasNavigationRoute
Indicates that one entity provides or defines a navigation path or route leading to or through another entity.
- 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 27, 2026, 5:49 a.m.