Triple
T2435694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johannesburg Stock Exchange |
E52954
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | JSE |
E161665
|
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: JSE | Statement: [Johannesburg Stock Exchange, abbreviation, JSE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: JSE Context triple: [Johannesburg Stock Exchange, abbreviation, JSE]
-
A.
JSC
JSC is NASA’s primary human spaceflight center in Houston, Texas, responsible for astronaut training, mission control, and spacecraft development.
-
B.
JSE Limited
chosen
JSE Limited is the Johannesburg-based stock exchange and the primary securities market for South Africa and much of the African continent.
-
C.
JST
JST is the time zone used throughout Japan, nine hours ahead of Coordinated Universal Time (UTC+9).
-
D.
JES2
JES2 (Job Entry Subsystem 2) is an IBM mainframe component that manages the input, scheduling, and output of batch jobs and print workloads in the z/OS operating system.
-
E.
JES3
JES3 is a mainframe job entry subsystem for IBM z/OS that manages and controls the scheduling, execution, and output of batch jobs across single or multiple 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_69ab4959bcc0819083246f9fb10439e3 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abc9cd49b48190bff10a5ab7cef483 |
completed | March 7, 2026, 6:46 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69aebf6e23088190b0ce2feaa3eddda4 |
completed | March 9, 2026, 12:39 p.m. |
Created at: March 6, 2026, 9:43 p.m.