Triple
T1182567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASEAN Regional Forum |
E25171
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | ARF |
E135249
|
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: ARF | Statement: [ASEAN Regional Forum, abbreviation, ARF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ARF Context triple: [ASEAN Regional Forum, abbreviation, ARF]
-
A.
ARF
chosen
ARF is a key multilateral security dialogue platform in the Asia-Pacific region that brings together ASEAN members and other major powers to discuss political and security issues.
-
B.
AFR
AFR is the ICAO airline designator used to identify Air France flights in international aviation operations.
-
C.
AFB
AFB is the commonly used abbreviation for the Belgian Armed Forces, the military organization responsible for Belgium’s national defense and international military commitments.
-
D.
AF
AF is the two-letter ISO 3166-1 alpha-2 country code assigned to Afghanistan for international standardization and referencing.
-
E.
AF
AF is the two-letter IATA airline designator assigned to Air France, the flag carrier of France.
- 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_69a494267b4c819088c97a59182bf56a |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd35fb888190adf1e5d0615fa725 |
completed | March 1, 2026, 10:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac764a5f508190a54c8f01cf0b0d11 |
completed | March 7, 2026, 7:02 p.m. |
Created at: March 1, 2026, 7:45 p.m.