Triple
T16404971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RJFU |
E398402
|
entity |
| Predicate | hasICAOCode |
P419
|
FINISHED |
| Object | RJFU |
E398402
|
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: RJFU | Statement: [RJFU, hasICAOCode, RJFU]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RJFU Context triple: [RJFU, hasICAOCode, RJFU]
-
A.
RJFU
chosen
RJFU is the ICAO airport code for Nagasaki Airport, a regional and international airport serving Nagasaki Prefecture in Japan.
-
B.
Japan Rugby Football Union
The Japan Rugby Football Union is the national governing body responsible for overseeing and developing rugby union in Japan, including its professional and international teams.
-
C.
Tenri University Rugby Football Club
Tenri University Rugby Football Club is a prominent Japanese university rugby union team known for its strong performances in national collegiate competitions.
-
D.
JFA
JFA is the governing body responsible for overseeing and organizing football activities and competitions in Jordan.
-
E.
JFA
JFA is the commonly used abbreviation for the Japan Football Association, the governing body for football in Japan.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e327d1f16481909adb19dab86dcc72 |
completed | April 18, 2026, 6:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a003c6094e481909aa7402fd17fedae |
completed | May 10, 2026, 8:05 a.m. |
Created at: April 10, 2026, 5:09 a.m.