Triple
T31025146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Detachment 1, 9th Strategic Reconnaissance Wing |
E790547
|
entity |
| Predicate | nicknameOfAircraftUsed |
P95769
|
FINISHED |
| Object | Habu |
—
|
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: Habu | Statement: [Detachment 1, 9th Strategic Reconnaissance Wing, nicknameOfAircraftUsed, Habu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nicknameOfAircraftUsed Context triple: [Detachment 1, 9th Strategic Reconnaissance Wing, nicknameOfAircraftUsed, Habu]
-
A.
aircraftNicknamedFor
chosen
Indicates that an aircraft is commonly known or referred to by a particular nickname derived from or inspired by something else.
-
B.
aircraftTypesUsedOn
Indicates the types or models of aircraft that are used on or assigned to a particular route, service, operation, or context.
-
C.
usedOnAircraftName
Indicates that something is employed or applied on an aircraft identified by a specific name.
-
D.
notableAircraftCallsign
Indicates that a particular aircraft is notably associated with, or commonly identified by, a specific callsign.
-
E.
aircraftNamedIs
Indicates that a specific aircraft has the given name or designation.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:58 p.m.