Triple

T26648330
Position Surface form Disambiguated ID Type / Status
Subject Preus Museum E668978 entity
Predicate locatedInFormerMilitaryArea P126626 FINISHED
Object Karljohansvern naval base NE NERFINISHED

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: Karljohansvern naval base | Statement: [Preus Museum, locatedInFormerMilitaryArea, Karljohansvern naval base]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedInFormerMilitaryArea
Context triple: [Preus Museum, locatedInFormerMilitaryArea, Karljohansvern naval base]
  • A. partOfMilitaryArea
    Indicates that one entity is located within or belongs to a designated military-controlled area of another entity.
  • B. hasFormerMilitaryInstallationNearby
    Indicates that an entity is located close to a site where a military installation previously existed but is no longer active.
  • C. formerMilitaryBase chosen
    Indicates that a location was previously used as a military base but no longer serves that function.
  • D. locatedInFormerMiningArea
    Indicates that an entity is situated within an area that was previously used for mining activities.
  • E. locatedOnMilitaryInstallation
    Indicates that one entity is physically situated within the boundaries of, or directly on, a military installation or base.
  • 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_69ee9d00eb5481908d6c6d0ada2f0c9a completed April 26, 2026, 11:17 p.m.
NER Named-entity recognition batch_69fdd2be648c8190b60b3d1caeb44364 completed May 8, 2026, 12:10 p.m.
PD Predicate disambiguation batch_69fdd14a5c708190a6f95ec61f4fc28f completed May 8, 2026, 12:04 p.m.
Created at: April 27, 2026, 2:32 a.m.