Triple
T18390744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Jordanian Air Force |
E449718
|
entity |
| Predicate | acronym |
P43
|
FINISHED |
| Object | RJAF |
—
|
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: RJAF | Statement: [Royal Jordanian Air Force, acronym, RJAF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RJAF Context triple: [Royal Jordanian Air Force, acronym, RJAF]
-
A.
RJAF
chosen
RJAF is the acronym for the Royal Jordanian Air Force, the aerial warfare branch of Jordan’s armed forces.
-
B.
RJAA
RJAA is the ICAO airport code for Narita International Airport, a major international gateway serving the Tokyo metropolitan area in Japan.
-
C.
RJA
RJA is the ICAO airline designator used for Royal Jordanian, the flag carrier airline of Jordan.
-
D.
Japan Air Self-Defense Force
The Japan Air Self-Defense Force is the aviation branch of Japan’s Self-Defense Forces, responsible for the country’s air defense and airspace security.
-
E.
RMAF
RMAF is the acronym commonly used to refer to the Royal Moroccan Air Force, the aerial warfare branch of Morocco’s armed forces.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e518422e488190bd06fad72efa1641 |
completed | April 19, 2026, 6 p.m. |
Created at: April 10, 2026, 10:46 a.m.