Triple
T5416824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Israeli Air Force |
E121152
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | IAF |
E121152
|
NE 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: IAF | Statement: [Israeli Air Force, shortName, IAF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IAF Context triple: [Israeli Air Force, shortName, IAF]
-
A.
FiAF
FiAF is the commonly used abbreviation for the Finnish Air Force, the air warfare branch of Finland’s Defence Forces.
-
B.
ISF
ISF is the primary institution in Israel that funds and promotes basic scientific research across a wide range of disciplines.
-
C.
Israeli Air Force
chosen
The Israeli Air Force is the aerial warfare branch of Israel’s military, known for its advanced technology, precision air operations, and pivotal role in the country’s defense and regional conflicts.
-
D.
RJAF
RJAF is the acronym for the Royal Jordanian Air Force, the aerial warfare branch of Jordan’s armed forces.
-
E.
FAI
FAI is the IATA airport code for Fairbanks International Airport, a major air transport hub serving Fairbanks and interior Alaska.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69bd463a41cc8190b32ff5af2b96ca93 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87bff75881909bdfd2cdf7ff5657 |
completed | March 20, 2026, 5:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf3aaaaae0819090db7071e9a5847a |
completed | March 22, 2026, 12:41 a.m. |
Created at: March 20, 2026, 2:05 p.m.