Triple

T1526760
Position Surface form Disambiguated ID Type / Status
Subject Fort Pickens E32352 entity
Predicate decommissionedAsCoastalFort P14100 FINISHED
Object 20th century 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: 20th century | Statement: [Fort Pickens, decommissionedAsCoastalFort, 20th century]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: decommissionedAsCoastalFort
Context triple: [Fort Pickens, decommissionedAsCoastalFort, 20th century]
  • A. decommissionedReason
    Indicates the reason or cause for which an entity, typically an asset or system, was taken out of service or formally retired.
  • B. decommissionedDate chosen
    Indicates the date on which an entity was formally taken out of service or retired from active use.
  • C. laterGarrisonedBy
    Indicates that a location or structure was subsequently occupied and used as a military garrison by a specified force or group.
  • D. strickenFromNavalRegister
    Indicates that a vessel has been officially removed from a navy’s active register, ending its status as a commissioned naval ship.
  • E. demolished
    Indicates that one entity completely destroyed or razed another entity, typically a structure or object, so that it no longer exists in its previous form.
  • 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_69a885e9b0ac819093a9806ad0efc82c completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a933ddc5a881909cdf503f2bc29bd4 completed March 5, 2026, 7:42 a.m.
PD Predicate disambiguation batch_69a907ae8f688190ad9000ea1e018585 completed March 5, 2026, 4:33 a.m.
Created at: March 4, 2026, 7:26 p.m.