Triple
T31716664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AGOR-27 class |
E809470
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | oceanographic research vessel class |
C12437
|
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: oceanographic research vessel class Context triple: [AGOR-27 class, instanceOf, oceanographic research vessel class]
-
A.
oceanographic research ship
chosen
An oceanographic research ship is a specialized vessel equipped with scientific instruments and laboratories for studying the physical, chemical, biological, and geological properties of the ocean.
-
B.
atmospheric research vessel
An atmospheric research vessel is a specialized mobile platform, such as an aircraft, balloon, or airship, equipped with scientific instruments to observe, sample, and analyze the properties and dynamics of planetary atmospheres.
-
C.
hydrographic survey vessel
A hydrographic survey vessel is a specialized ship equipped with advanced sensors and instruments to measure and map the physical features of oceans, seas, and other bodies of water for navigation, research, and resource management.
-
D.
oceanographic research infrastructure
Oceanographic research infrastructure comprises the specialized vessels, instruments, platforms, data systems, and support facilities used to observe, measure, and analyze physical, chemical, biological, and geological processes in the ocean.
-
E.
exploration vessel
An exploration vessel is a specialized craft designed to travel into unknown or remote regions to gather data, conduct research, and support long-duration exploratory missions.
- 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_69f348df4e048190a4a5a9932ada78d6 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:17 p.m.