Triple
T16618699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BCT |
E403762
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | BCT |
unclear NED1
|
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: BCT | Statement: [BCT, abbreviation, BCT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BCT Context triple: [BCT, abbreviation, BCT]
-
A.
BCT
BCT is the Central Bank of Tunisia, the country’s primary monetary authority responsible for issuing currency and overseeing financial stability.
-
B.
BCT
BCT is the railway station code for Mumbai Central, a major terminus on the Western Railway network in Mumbai, India.
-
C.
BCT
BCT is the initial military training program that transforms civilian recruits into basic soldiers by teaching fundamental combat, discipline, and physical fitness skills.
-
D.
BTR
BTR is the three-letter IATA airport code for Baton Rouge Metropolitan Airport in Baton Rouge, Louisiana.
-
E.
BPC
BPC is the commonly used abbreviation for the Bryant Park Corporation, the nonprofit organization that manages and maintains Bryant Park in New York City.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide. chosen
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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3754bc4cc8190a586732fc6507b40 |
completed | April 18, 2026, 12:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a007db0b4348190beb573bc3df98125 |
completed | May 10, 2026, 12:44 p.m. |
Created at: April 10, 2026, 5:17 a.m.