Triple
T14082164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamil Nadu Legislative Assembly |
E338893
|
entity |
| Predicate | acronym |
P43
|
FINISHED |
| Object | TNLA |
E338893
|
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: TNLA | Statement: [Tamil Nadu Legislative Assembly, acronym, TNLA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TNLA Context triple: [Tamil Nadu Legislative Assembly, acronym, TNLA]
-
A.
TNLA
chosen
TNLA is the commonly used acronym for the Tamil Nadu Legislative Assembly, the unicameral law-making body of the Indian state of Tamil Nadu.
-
B.
NLA
NLA refers to Switzerland’s top professional ice hockey league, known for featuring high-level European competition.
-
C.
TLA
TLA is a formal specification language developed by Leslie Lamport for describing and reasoning about concurrent and distributed systems using temporal logic.
-
D.
TN
TN is a UK postcode area covering Tunbridge Wells and surrounding parts of Kent and East Sussex.
-
E.
TN
TN is the official two-letter U.S. Postal Service abbreviation for the state of Tennessee.
- 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5c5f759c81909bfd60ab35b0937b |
completed | April 14, 2026, 3:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcb6749c3c81909833a0b6ddcae3fb |
completed | May 7, 2026, 3:57 p.m. |
Created at: April 9, 2026, 10:21 p.m.