Triple
T8673339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assam Rifles |
E205852
|
entity |
| Predicate | usesAbbreviation |
P43
|
FINISHED |
| Object | AR |
E205852
|
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: AR | Statement: [Assam Rifles, usesAbbreviation, AR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: AR Context triple: [Assam Rifles, usesAbbreviation, AR]
-
A.
AR
AR is the commonly used abbreviation for the Assembly of the Republic, the unicameral national parliament of Portugal.
-
B.
AR
AR is the standard abbreviation for the Romanian Academy, the leading national institution for the promotion of science, culture, and the arts in Romania.
-
C.
AR
AR is the two-letter IATA airline designator assigned to Aerolíneas Argentinas, the flag carrier of Argentina.
-
D.
AR
chosen
AR is the commonly used abbreviation for the Assam Rifles, a paramilitary force of India responsible for security and counterinsurgency operations in the Northeast region.
-
E.
AR
AR is the commonly used abbreviation for Adventist Review, a leading magazine of the Seventh-day Adventist Church.
- 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_69ca83529a9c8190b5c075b4f14636ed |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc491b807c81909563a34a947bc21a |
completed | March 31, 2026, 10:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cef3960ce881908f07fb9fdafcd550 |
completed | April 2, 2026, 10:54 p.m. |
Created at: March 30, 2026, 6:31 p.m.