Triple
T6549112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People's Security Army |
E151083
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | TKR |
E151083
|
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: TKR | Statement: [People's Security Army, hasAbbreviation, TKR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TKR Context triple: [People's Security Army, hasAbbreviation, TKR]
-
A.
TKR
chosen
TKR is the abbreviated name of the People's Security Army, a military or paramilitary organization associated with internal security and defense.
-
B.
TKA
TKA is a regional vehicle registration code used on license plates for cars registered in the Kazimierza Wielka area of Poland.
-
C.
TKF
TKF is the IATA airport code for Truckee Tahoe Airport, a general aviation airport serving the Truckee and Lake Tahoe region in California, USA.
-
D.
TKM
TKM is the three-letter ISO 3166-1 alpha-3 country code assigned to Turkmenistan.
-
E.
TK
TK is the two-letter IATA airline designator used to identify Turkish Airlines in global aviation systems.
- 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_69c687f3fd60819083bfa583e5bcfa71 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ae037c488190b9441f9a9e7a69b6 |
completed | March 27, 2026, 4:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6e4214f28819083134e9e6fe6f393 |
completed | March 27, 2026, 8:10 p.m. |
Created at: March 27, 2026, 1:51 p.m.