Triple

T405091
Position Surface form Disambiguated ID Type / Status
Subject Hunter Army Airfield E9365 entity
Predicate FAAcode P420 FINISHED
Object SVN E51340 NE 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: SVN | Statement: [Hunter Army Airfield, FAAcode, SVN]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SVN
Context triple: [Hunter Army Airfield, FAAcode, SVN]
  • A. SVN chosen
    SVN is the IATA airport code for Hunter Army Airfield, a U.S. military airfield located near Savannah, Georgia.
  • B. Git
    Git is a widely used distributed version control system designed to efficiently track changes in source code and support collaborative software development.
  • C. Channelside
    Channelside is a waterfront entertainment and residential district in downtown Tampa, Florida, known for its restaurants, nightlife, and proximity to the cruise port.
  • D. GitHub
    GitHub is a widely used web-based platform for version control and collaborative software development, built around the Git system and popular among open-source and enterprise projects.
  • E. SVR
    SVR is the set of post-nominal letters used to denote recipients of the Order of the White Rose of Finland.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69a2e8004cb88190b92ed1add6abf41a completed Feb. 28, 2026, 1:05 p.m.
NER Named-entity recognition batch_69a2eca37fe881909802126952dfdd59 completed Feb. 28, 2026, 1:24 p.m.
NED1 Entity disambiguation (via context triple) batch_69a41774cd008190a254facf9cba90b6 completed March 1, 2026, 10:39 a.m.
Created at: Feb. 28, 2026, 1:08 p.m.