Triple
T15836878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bell OH-58 Kiowa |
E384006
|
entity |
| Predicate | statusInUSArmy |
P65983
|
FINISHED |
| Object | retired |
—
|
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: retired | Statement: [Bell OH-58 Kiowa, statusInUSArmy, retired]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInUSArmy Context triple: [Bell OH-58 Kiowa, statusInUSArmy, retired]
-
A.
militaryStatus
Indicates the relationship between an entity and a military organization in terms of service condition, such as active duty, reserve, veteran, or non-military status.
-
B.
hasMilitaryStatus
chosen
Indicates that an entity possesses a specific military affiliation, role, or status (such as active duty, reserve, or veteran).
-
C.
correspondingRankInUSArmy
Indicates that one military rank is the equivalent or closest matching rank within the hierarchy of the United States Army.
-
D.
militaryRankEligibility
Indicates that one entity is qualified or permitted to hold, attain, or be considered for a specified military rank.
-
E.
statusInUnitedStates
Indicates the legal or official standing that an entity holds within the jurisdiction of the United States.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e142e1fcd48190bcb884f6c65db847 |
completed | April 16, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.