Triple

T21879461
Position Surface form Disambiguated ID Type / Status
Subject SNJ E540239 entity
Predicate tailCodeSystem P95403 FINISHED
Object U.S. Navy pre-1962 designation system 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: U.S. Navy pre-1962 designation system | Statement: [SNJ, tailCodeSystem, U.S. Navy pre-1962 designation system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: tailCodeSystem
Context triple: [SNJ, tailCodeSystem, U.S. Navy pre-1962 designation system]
  • A. standardCodeSystem chosen
    Indicates that an entity uses or is associated with a recognized, authoritative coding or classification system as its reference standard.
  • B. regionCodeSystem
    Indicates that a region is identified or classified according to a particular coding system for geographic or administrative areas.
  • C. tailCodePrefix
    Indicates that one entity’s tail code begins with, or is prefixed by, the string represented by the other entity.
  • D. administrativeCodeSystem
    Indicates that there is a system or scheme used to assign and manage administrative codes for organizing or identifying entities or records.
  • E. relatedCodeSet
    Indicates that one code set is associated with or connected to another code set in a meaningful or defined way.
  • 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_69e0c479a98081908ce333853fdd4348 completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f118e42c108190b6308016655c429e completed April 28, 2026, 8:30 p.m.
PD Predicate disambiguation batch_69e6be9394f88190945ddd1dc004d29d completed April 21, 2026, 12:02 a.m.
Created at: April 16, 2026, 7:04 p.m.