Triple

T6276995
Position Surface form Disambiguated ID Type / Status
Subject Quentin Roosevelt Boulevard E140684 entity
Predicate hasEponymCauseOfDeath P69814 FINISHED
Object combat-related aircraft shootdown 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: combat-related aircraft shootdown | Statement: [Quentin Roosevelt Boulevard, hasEponymCauseOfDeath, combat-related aircraft shootdown]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasEponymCauseOfDeath
Context triple: [Quentin Roosevelt Boulevard, hasEponymCauseOfDeath, combat-related aircraft shootdown]
  • A. hasEponymConnectionTo
    Indicates that one entity is named after, derived from, or otherwise linguistically or honorifically connected to another entity as its eponym.
  • B. sharesEponymWith
    Indicates that two entities are named after the same person, place, or thing (i.e., they share the same eponym).
  • C. eponymFor
    Indicates that one entity gives its name to another entity, which is then named after it.
  • D. hadEponymousAncestor
    Indicates that an entity has an ancestor whose name it shares or from whom its own name is derived.
  • E. isNamedForEponymRole
    Indicates that one entity bears a name derived from another entity that serves as its eponym or namesake.
  • F. None of above. chosen

Provenance (4 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_69c008cc158881908df6ec94a911c736 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c063d96fbc8190a9091456b82762d1 completed March 22, 2026, 9:49 p.m.
PD Predicate disambiguation batch_69c05608a5608190b22a1fdc4060470d completed March 22, 2026, 8:50 p.m.
PDg Predicate description generation batch_69c05b37ac1881909e947822490ba4f2 completed March 22, 2026, 9:12 p.m.
Created at: March 22, 2026, 4:26 p.m.