Triple

T15857910
Position Surface form Disambiguated ID Type / Status
Subject ECRS radar family E384507 entity
Predicate hasMember P10 FINISHED
Object ECRS Mk2 E384507 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: ECRS Mk2 | Statement: [ECRS radar family, hasMember, ECRS Mk2]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ECRS Mk2
Context triple: [ECRS radar family, hasMember, ECRS Mk2]
  • A. ECRS Mk0
    ECRS Mk0 is an advanced variant of the CAPTOR radar system designed to enhance fighter aircraft’s air-to-air and air-to-ground detection, tracking, and targeting capabilities.
  • B. ECRS radar family chosen
    The ECRS radar family is a series of advanced European Active Electronically Scanned Array (AESA) radars developed for modern fighter aircraft, notably the Eurofighter Typhoon.
  • C. MK 2
    MK 2 is the small natural satellite orbiting the distant dwarf planet Makemake in the Kuiper Belt.
  • D. ES-3A Shadow
    The ES-3A Shadow is a carrier-based electronic reconnaissance and signals intelligence variant of the S-3 Viking used by the U.S. Navy for over-the-horizon surveillance and electronic support measures.
  • E. M-52
    M-52 is a state highway in Michigan that runs north–south through several counties, serving as an important regional route for local and through traffic.
  • 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_69d86da422088190aac39e32e6c68429 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e1555808688190882b610109d1e5f4 completed April 16, 2026, 9:32 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffb03c8cb081908c18c7b2d143c4b4 completed May 9, 2026, 10:07 p.m.
Created at: April 10, 2026, 4:50 a.m.