Triple
T3312763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States lighthouse districts |
E69610
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime administration system |
C4267
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: maritime administration system Context triple: [United States lighthouse districts, instanceOf, maritime administration system]
-
A.
maritime navigation authority
chosen
A maritime navigation authority is an organization responsible for regulating, managing, and ensuring the safety and efficiency of vessel movements and navigational systems within designated waters.
-
B.
naval administrative office
A naval administrative office is an organizational unit responsible for managing the paperwork, personnel records, logistics, and regulatory compliance that support the operations of a navy or naval installation.
-
C.
maritime convoy system
A maritime convoy system is an organized method of grouping and coordinating multiple ships under shared routing, scheduling, and protection protocols to enhance safety, security, and efficiency during sea transit.
-
D.
maritime convoy system
A maritime convoy system is an organized method of grouping merchant or military vessels to sail together under coordinated protection and navigation to reduce risks from threats such as enemy attacks, piracy, or hazardous conditions.
-
E.
naval office
A naval office is an administrative entity within a navy responsible for managing operations, logistics, personnel, and documentation related to maritime military activities.
- F. None of above.
Provenance (1 batch)
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_69ad85a0bb048190a5458d2738012d61 |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:11 p.m.