Triple
T36333802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Range Navigation |
E894724
|
entity |
| Predicate | LORAN-CChainStructure |
P173130
|
FINISHED |
| Object | master and secondary stations |
—
|
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: master and secondary stations | Statement: [Long Range Navigation, LORAN-CChainStructure, master and secondary stations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: LORAN-CChainStructure Context triple: [Long Range Navigation, LORAN-CChainStructure, master and secondary stations]
-
A.
hasSatelliteConstellation
Indicates that an entity possesses or operates a specific group of satellites functioning together as a coordinated constellation.
-
B.
radioStructure
chosen
Indicates a structural or organizational relationship involving radio components, systems, or configurations.
-
C.
lapStructure
Indicates that one entity forms a lap-like structural surface or support upon which another entity can rest or be positioned.
-
D.
satelliteSystem
Indicates a relationship where one system functions as a satellite or subordinate system orbiting, supporting, or depending on another primary system.
-
E.
navigationAidIdentifier
Indicates that an entity is assigned or associated with an identifier used to uniquely reference a specific navigation aid.
- 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_69f76e4e90148190b02fe52593c70b5b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:09 p.m.