Triple
T8542111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pula–thebe system |
E202221
|
entity |
| Predicate | subunit |
P35
|
FINISHED |
| Object | thebe |
E39503
|
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: thebe | Statement: [pula–thebe system, subunit, thebe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: thebe Context triple: [pula–thebe system, subunit, thebe]
-
A.
thebe
chosen
The thebe is the fractional monetary unit of Botswana, representing one-hundredth of a Botswana pula.
-
B.
TEB
TEB is the IATA airport code for Teterboro Airport, a major general aviation and corporate jet airport serving the New York City metropolitan area in New Jersey.
-
C.
JupyterLab
JupyterLab is a web-based interactive development environment for working with Jupyter notebooks, code, and data.
-
D.
beamer
Beamer is a LaTeX document class used for creating professional presentation slides.
-
E.
Repyt
Repyt is an ancient Egyptian lioness goddess primarily worshipped at Akhmim, associated with protection and sometimes linked to solar and warlike aspects.
- 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_69ca832461e88190a654c5e44e233aa8 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6e26be48190b10bc62fad178dad |
completed | March 31, 2026, 3:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce6da3d65c819087ed6b46dfc35885 |
completed | April 2, 2026, 1:22 p.m. |
Created at: March 30, 2026, 6:18 p.m.