Triple
T22472931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air and Space Achievement Medal |
E555551
|
entity |
| Predicate | combatEligible |
P61973
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Air and Space Achievement Medal, combatEligible, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatEligible Context triple: [Air and Space Achievement Medal, combatEligible, false]
-
A.
combatantRequirement
Indicates a condition or qualification that an entity must meet in order to participate as a combatant in a conflict or battle.
-
B.
hasCombat
Indicates that an entity engages in, is involved with, or possesses the capability for combat or fighting interactions with other entities.
-
C.
combatOrNonCombat
chosen
Indicates whether an entity is involved in combat activities or is in a non-combat role or situation.
-
D.
combatBy
Indicates a relationship where one entity engages in combat or fighting through the agency, actions, or involvement of another entity.
-
E.
combatantsIncluded
Indicates that the specified entities are participants or parties involved in a particular combat or conflict.
- 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_69e11e52c2048190952dc5df209b9bed |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15be2034c81909d1263f2ed114b46 |
completed | April 29, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:49 p.m.