Triple

T3817459
Position Surface form Disambiguated ID Type / Status
Subject Front Royal–Warren County Airport E84290 entity
Predicate hasFAACode P34770 FINISHED
Object FRR E390312 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: FRR | Statement: [Front Royal–Warren County Airport, hasFAACode, FRR]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: FRR
Context triple: [Front Royal–Warren County Airport, hasFAACode, FRR]
  • A. FRR chosen
    FRR is the IATA airport code for Front Royal–Warren County Airport, a public airport serving the Front Royal area in Virginia, United States.
  • B. FFR
    FFR is the commonly used abbreviation for the French Rugby Federation, the governing body for rugby union in France.
  • C. FFRRO
    FFRRO is a U.S. Environmental Protection Agency office that oversees the cleanup, restoration, and reuse of contaminated federal facilities such as military bases and government sites.
  • D. FRD
    FRD is the station code for a railway station named after U.S. President Franklin D. Roosevelt.
  • E. RRF
    RRF is the acronym for the United States Ready Reserve Force, a fleet of government-owned cargo ships maintained for rapid activation in military and humanitarian sealift operations.
  • 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_69aed931f5908190be2c07af66d4df25 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aee8e1852c8190b61c507a7128d4c6 completed March 9, 2026, 3:36 p.m.
NED1 Entity disambiguation (via context triple) batch_69b503f549b0819088b64ddb3f38238f completed March 14, 2026, 6:45 a.m.
Created at: March 9, 2026, 3:17 p.m.