Triple
T4319131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tankies |
E96466
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | RTR |
E366335
|
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: RTR | Statement: [The Tankies, hasAbbreviation, RTR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RTR Context triple: [The Tankies, hasAbbreviation, RTR]
-
A.
RTR
chosen
RTR is the commonly used nickname for the Recruit Training Regiment, a military unit responsible for initial training of new recruits.
-
B.
TRR
TRR is the IATA airport code for Trincomalee Airport in Sri Lanka.
-
C.
TRTS
TRTS is the commonly used abbreviation for the Taipei Metro rapid transit system serving the Taipei metropolitan area in Taiwan.
-
D.
RTA
RTA is Dubai’s Roads and Transport Authority, the government agency responsible for planning and operating the emirate’s public transportation and road systems.
-
E.
RTA
RTA is the common abbreviation for the Regional Transportation Authority of Northeastern Illinois, the agency that oversees public transit services in 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_69b345422aac81909ddbadae437d122e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35112ec008190958487f501481887 |
completed | March 12, 2026, 11:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5d089ab5c8190ba1691f8ce9b7b4f |
completed | March 14, 2026, 9:18 p.m. |
Created at: March 12, 2026, 11:12 p.m.