Triple
T17770782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IHO S-129 |
E443630
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | S-129 |
—
|
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: S-129 | Statement: [IHO S-129, shortName, S-129]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: S-129 Context triple: [IHO S-129, shortName, S-129]
-
A.
S-124
S-124 is an IHO product specification that defines the digital format and structure for broadcasting maritime navigational warnings in modern e-navigation systems.
-
B.
S-125
The S-125 is a Soviet-era short- to medium-range surface-to-air missile system designed for low- to medium-altitude air defense against aircraft and cruise missiles.
-
C.
S-129 UKCM
chosen
S-129 UKCM is a standardized Under Keel Clearance Management product specification used in maritime navigation to ensure safe vessel under-keel clearance.
-
D.
S-102
S-102 is an IHO S-100 series standard that defines high-resolution bathymetric surface data for use in modern electronic navigation and marine applications.
-
E.
S120
S120 is the pennant number of HMS Ambush, a British Royal Navy Astute-class nuclear-powered attack submarine.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e485ff928481909fe32260ba57978f |
completed | April 19, 2026, 7:36 a.m. |
Created at: April 10, 2026, 10:11 a.m.