Triple
T1785378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F-15 Eagle |
E39378
|
entity |
| Predicate | combatRecord |
P32376
|
FINISHED |
| Object | very high kill-to-loss ratio |
—
|
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: very high kill-to-loss ratio | Statement: [F-15 Eagle, combatRecord, very high kill-to-loss ratio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatRecord Context triple: [F-15 Eagle, combatRecord, very high kill-to-loss ratio]
-
A.
battleHonors
Indicates that an entity has been awarded or is associated with specific honors or distinctions earned through participation in battles or military engagements.
-
B.
battledIn
Indicates that two or more entities engaged in a battle or conflict that took place at a specific location or during a particular event.
-
C.
associatedWithBattle
Indicates a relationship where an entity is connected or linked to a specific battle, such as by participation, relevance, or involvement.
-
D.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
E.
notableBattleRole
Indicates the specific role or function an entity played in a notable or historically significant battle.
- 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_69a88630519c8190a17addd83c4a3ef4 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab75457e54819096b8c6ae8c65550c |
completed | March 7, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69aa61d165688190924962a98e07ff69 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab75444d28819091c393e62fc97f82 |
completed | March 7, 2026, 12:45 a.m. |
Created at: March 4, 2026, 7:31 p.m.