Triple
T18777287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RRS |
E459162
|
entity |
| Predicate | maritimePrefixType |
P80388
|
FINISHED |
| Object | research vessel prefix |
—
|
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: research vessel prefix | Statement: [RRS, maritimePrefixType, research vessel prefix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritimePrefixType Context triple: [RRS, maritimePrefixType, research vessel prefix]
-
A.
maritimeVariant
Indicates a version or form of something that is specifically adapted for or used in maritime (sea-related) contexts.
-
B.
navyDesignationPrefix
chosen
Indicates the specific naval designation or prefix assigned to an entity, typically reflecting its role, type, or status within a navy.
-
C.
portOfRegistryFor
Indicates that one entity serves as the official port where another entity (typically a vessel) is registered.
-
D.
maritimeFunction
Indicates a relationship where an entity serves a role, purpose, or operational function specifically within maritime contexts such as sea transport, navigation, or marine activities.
-
E.
maritimeInfrastructure
Indicates the existence, presence, or involvement of facilities, structures, or systems that support maritime activities such as shipping, ports, and coastal operations between the related entities.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5933c640081909bb6fbaa1a21d411 |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.