Triple
T3404681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond International Airport |
E71742
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | RIC |
E355218
|
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: RIC | Statement: [Richmond International Airport, FAAcode, RIC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RIC Context triple: [Richmond International Airport, FAAcode, RIC]
-
A.
RIC
RIC is the standard abbreviation used for the Richmond Flying Squirrels, a Minor League Baseball team based in Richmond, Virginia.
-
B.
RIC
RIC is a regulatory information circular or compliance framework reference used in the context of U.S. maritime safety and towing vessel regulations under Subchapter M.
-
C.
RIC
chosen
RIC is the three-letter IATA airport code for Richmond International Airport, serving the Richmond, Virginia metropolitan area.
-
D.
RI
RI is the standard two-letter United States Postal Service abbreviation for the state of Rhode Island.
-
E.
RID
RID is the commonly used abbreviation for the Rock Island District, a commuter rail line serving the Chicago metropolitan area.
- 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_69ad85aac4808190a092c9cc8911f584 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb8eaa41c819095a4d51aec074649 |
completed | March 8, 2026, 5:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b35468916c8190ba6caa2c53e01d9c |
completed | March 13, 2026, 12:03 a.m. |
Created at: March 8, 2026, 3:14 p.m.