Triple
T6363223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Jordanian |
E143161
|
entity |
| Predicate | ICAOCode |
P419
|
FINISHED |
| Object | RJA |
E143160
|
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: RJA | Statement: [Royal Jordanian, ICAOCode, RJA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RJA Context triple: [Royal Jordanian, ICAOCode, RJA]
-
A.
RJA
chosen
RJA is the ICAO airline designator used for Royal Jordanian, the flag carrier airline of Jordan.
-
B.
RJAA
RJAA is the ICAO airport code for Narita International Airport, a major international gateway serving the Tokyo metropolitan area in Japan.
-
C.
RJAF
RJAF is the acronym for the Royal Jordanian Air Force, the aerial warfare branch of Jordan’s armed forces.
-
D.
RJAH
RJAH is the ICAO airport code for Hyakuri Air Base, a Japanese military airfield in Ibaraki Prefecture.
-
E.
RJ
RJ is the two-letter IATA airline designator assigned to Royal Jordanian, the flag carrier airline of Jordan.
- 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_69c008d7a9c4819098d647ec47776917 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0680d51a4819098a6bcd3dfd73be4 |
completed | March 22, 2026, 10:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c62d73a6ac8190a02602c3506e4226 |
completed | March 27, 2026, 7:10 a.m. |
Created at: March 22, 2026, 4:32 p.m.