Triple
T3065549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Catherine's Lighthouse |
E62095
|
entity |
| Predicate | navigationSystemType |
P35891
|
FINISHED |
| Object | visual navigation aid |
—
|
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: visual navigation aid | Statement: [St Catherine's Lighthouse, navigationSystemType, visual navigation aid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationSystemType Context triple: [St Catherine's Lighthouse, navigationSystemType, visual navigation aid]
-
A.
navigationSystemComponent
Indicates that one entity functions as a component or subpart of a navigation system associated with another entity.
-
B.
navigationType
Indicates the method or mode by which movement or traversal is carried out between locations or through an environment.
-
C.
hasNavigationTechnology
chosen
Indicates that an entity is equipped with or utilizes a system or technology for determining or guiding its position, route, or movement.
-
D.
driveType
Indicates the type or configuration of the drive mechanism used to power or propel an entity.
-
E.
navigation
Indicates the act or process of determining and following a path or route from one location or state to another.
- 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_69ad85793e5c8190a358049bc4a98d8c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada0fc01dc81908fbdf7c1ef73afe4 |
completed | March 8, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69ad9624b7a0819091d255614f5819ea |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.