Triple

T37390691
Position Surface form Disambiguated ID Type / Status
Subject Gloster Gamecock E928695 entity
Predicate enteredRAFFrontlineService P182876 FINISHED
Object No. 23 Squadron RAF NE NERFINISHED

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: No. 23 Squadron RAF | Statement: [Gloster Gamecock, enteredRAFFrontlineService, No. 23 Squadron RAF]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: enteredRAFFrontlineService
Context triple: [Gloster Gamecock, enteredRAFFrontlineService, No. 23 Squadron RAF]
  • A. enteredFrontlineService chosen
    Indicates that an entity began active operational duty or participation on the primary line of activity or conflict.
  • B. enteredRAFService
    Indicates that an entity began service in the Royal Air Force (RAF).
  • C. frontLineService
    Indicates that an entity provides direct, first-contact service or support to customers, clients, or the public.
  • D. frontlineService
    Indicates that an entity provides direct, first-point-of-contact service or support to end users or customers.
  • E. enteredService
    Indicates that an entity began active use or operation at a specific time or in a specific context.
  • 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_69f76ebb10c481909b54b9dba263e29f completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fcc7338120819081cb46547d60f2cb completed May 7, 2026, 5:09 p.m.
PD Predicate disambiguation batch_69fcc58566a0819082d5ea36e03bf0c6 completed May 7, 2026, 5:01 p.m.
Created at: May 3, 2026, 4:16 p.m.