Triple
T17072990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4th Battalion, Royal Australian Regiment |
E414267
|
entity |
| Predicate | nickname |
P55
|
FINISHED |
| Object | 4 RAR |
E406829
|
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: 4 RAR | Statement: [4th Battalion, Royal Australian Regiment, nickname, 4 RAR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 4 RAR Context triple: [4th Battalion, Royal Australian Regiment, nickname, 4 RAR]
-
A.
RAR
RAR is the IATA airport code for Rarotonga International Airport, the main air gateway to the Cook Islands in the South Pacific.
-
B.
RAR
chosen
RAR is the Royal Australian Regiment, the principal regular infantry regiment of the Australian Army known for its service in major conflicts since World War II.
-
C.
4R
4R is a designated runway number used at airports, indicating a right-hand runway aligned roughly with a 040-degree magnetic heading.
-
D.
R4
R4 is a government office building in Oslo that forms part of Norway’s central Regjeringskvartalet complex.
-
E.
R4
R4 is a commuter rail line in the Rodalies de Catalunya network serving key suburban and regional routes in Catalonia, Spain.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbc28fec81909c39d432094d9cdd |
completed | April 18, 2026, 7:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a012ede108881909ddd0455be53ffac |
completed | May 11, 2026, 1:20 a.m. |
Created at: April 10, 2026, 5:34 a.m.