Triple
T38059731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shanwick Oceanic FIR |
E950306
|
entity |
| Predicate | usesNavigationSpecification |
P14917
|
FINISHED |
| Object | RNP4 |
—
|
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: RNP4 | Statement: [Shanwick Oceanic FIR, usesNavigationSpecification, RNP4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesNavigationSpecification Context triple: [Shanwick Oceanic FIR, usesNavigationSpecification, RNP4]
-
A.
hasNavigationUse
chosen
Indicates that something is used for navigation or serves a navigational function in relation to another entity.
-
B.
navigatesUsing
Indicates that one entity moves or travels through an environment by relying on another entity as its means, tool, or method of navigation.
-
C.
hasNavigationPurpose
Indicates that something exists or is designed specifically to serve a navigational function or goal.
-
D.
hasNavigationPass
Indicates that an entity possesses a valid authorization or pass granting it navigation or passage rights within a specified area or route.
-
E.
hasNavigationSpan
Indicates that one entity includes or is associated with a specific navigational range or segment used for movement or routing.
- 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.