Triple
T4400420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trier |
E93600
|
entity |
| Predicate | hasTwinTown |
P919
|
FINISHED |
| Object | Pula |
E262587
|
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: Pula | Statement: [Trier, hasTwinTown, Pula]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pula Context triple: [Trier, hasTwinTown, Pula]
-
A.
Pula
chosen
Pula is a historic coastal city in Croatia known for its well-preserved Roman amphitheater and Adriatic seaside location.
-
B.
Kwaluseni
Kwaluseni is a town in Eswatini known primarily as the main campus site of the University of Eswatini.
-
C.
Lobamba
Lobamba is the traditional and legislative capital of Eswatini, serving as the seat of the Swazi monarchy and key national institutions.
-
D.
Lanseria
Lanseria is a town in the northwestern part of Johannesburg, South Africa, known primarily for hosting the privately owned Lanseria International Airport.
-
E.
Gcaleka
Gcaleka is a prominent royal clan of the Xhosa people, historically associated with leadership and the Gcaleka sub-group in the Eastern Cape region of South Africa.
- 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_69b345158c748190a2c040fce2da9980 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b352cd71ec8190a62320fd072f744f |
completed | March 12, 2026, 11:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5f5f2310c8190934ba9768b68dd45 |
completed | March 14, 2026, 11:57 p.m. |
Created at: March 12, 2026, 11:28 p.m.