Triple
T5480299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RTP |
E123450
|
entity |
| Predicate | hasProfile |
P9523
|
FINISHED |
| Object | AVP |
E470892
|
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: AVP | Statement: [RTP, hasProfile, AVP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: AVP Context triple: [RTP, hasProfile, AVP]
-
A.
AVP
chosen
AVP is the three-letter IATA airport code for Wilkes-Barre/Scranton International Airport in Pennsylvania, USA.
-
B.
AV
AV is the two-letter IATA airline designator assigned to Avianca, the flag carrier of Colombia and one of Latin America’s largest airlines.
-
C.
AVS
AVS is a professional society focused on advancing the science and technology of materials, interfaces, and processing through research, education, and collaboration.
-
D.
AVV
AVV is the IATA airport code for Avalon Airport, a regional airport serving the Geelong and Melbourne areas in Victoria, Australia.
-
E.
ÁVH
ÁVH was the secret police and state security organization of communist Hungary, notorious for its role in political repression and surveillance during the early Cold War era.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9248ca348190aa116cace0f9b07a |
completed | March 20, 2026, 6:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf48a2880c8190ad76cf8c3862aede |
completed | March 22, 2026, 1:40 a.m. |
Created at: March 20, 2026, 2:09 p.m.