Triple
T14249519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ameerpet |
E353219
|
entity |
| Predicate | vehicleRegistrationCode |
P1173
|
FINISHED |
| Object | TS |
E756952
|
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: TS | Statement: [Ameerpet, vehicleRegistrationCode, TS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TS Context triple: [Ameerpet, vehicleRegistrationCode, TS]
-
A.
TS
TS is the Technical Secretariat of the Organisation for the Prohibition of Chemical Weapons, the body responsible for implementing and verifying compliance with the Chemical Weapons Convention.
-
B.
TS
TS is the IATA airline designator assigned to Air Transat, a Canadian leisure airline based in Montreal.
-
C.
TS
TS is the common abbreviation for Windows Terminal Services, Microsoft’s legacy remote desktop and application virtualization technology for Windows servers.
-
D.
TS
TS is a postcode area in northeastern England covering parts of Teesside, including towns such as Stockton-on-Tees and Middlesbrough.
-
E.
TS
chosen
TS is the vehicle registration code used on license plates for the Traunstein district in Bavaria, Germany.
- 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6295ef9081909cfb0c1283bca21a |
completed | April 14, 2026, 3:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd325815d48190b070866f41986847 |
completed | May 8, 2026, 12:46 a.m. |
Created at: April 10, 2026, 1:08 a.m.