Triple
T22078467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haakonsvern Naval Base |
E545582
|
entity |
| Predicate | hasTypeOfVessels |
P11978
|
FINISHED |
| Object | frigates |
—
|
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: frigates | Statement: [Haakonsvern Naval Base, hasTypeOfVessels, frigates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfVessels Context triple: [Haakonsvern Naval Base, hasTypeOfVessels, frigates]
-
A.
hasVesselType
chosen
Indicates that an entity is associated with or classified by a specific type of vessel (e.g., ship, boat, or container).
-
B.
hasVessel
Indicates that one entity possesses, uses, or is associated with a particular vessel (such as a container, ship, or transport medium) in the context of the described relationship or action.
-
C.
usesVesselType
Indicates that an entity performs an activity or operation by employing a specific type or category of vessel.
-
D.
vesselTypeServedOn
Indicates the type of vessel on which an entity has served or performed duty.
-
E.
sponsoredVesselType
Indicates that one entity has provided sponsorship or financial backing specifically for a vessel of a given type.
- 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_69e11e3523488190badd54b5d580c00d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128b43df0819090c248ded98fad12 |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e6f64a6a70819089d1a6c3a2384861 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:28 p.m.