Triple
T23365951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basotho Kingdom |
E593319
|
entity |
| Predicate | usedFortress |
P135201
|
FINISHED |
| Object | Thaba Bosiu |
—
|
NE NERFINISHED |
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: Thaba Bosiu | Statement: [Basotho Kingdom, usedFortress, Thaba Bosiu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedFortress Context triple: [Basotho Kingdom, usedFortress, Thaba Bosiu]
-
A.
usedFortificationsAt
Indicates that an entity employed or deployed specific fortifications in a particular context, such as a battle, campaign, or defensive situation.
-
B.
fortressUsedAs
chosen
Indicates that one entity functions or is employed in the role of a fortress for another entity or purpose.
-
C.
containsFortress
Indicates that a location or area includes a fortress within its boundaries.
-
D.
fortifiedBuilding
Indicates that a building is strengthened or reinforced for defense against attacks or intrusions.
-
E.
wasFortifiedBy
Indicates that a place or structure received defensive strengthening or fortification through the actions or resources of a specified agent or entity.
- F. None of above.
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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a0ac7494819082e98ac5632eba28 |
completed | April 29, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:31 p.m.