Triple
T1183469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mapungubwe Cultural Landscape |
E25192
|
entity |
| Predicate | mainOccupationPeriod |
P2912
|
FINISHED |
| Object | c. 1220–1290 CE |
—
|
LITERAL 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: c. 1220–1290 CE | Statement: [Mapungubwe Cultural Landscape, mainOccupationPeriod, c. 1220–1290 CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainOccupationPeriod Context triple: [Mapungubwe Cultural Landscape, mainOccupationPeriod, c. 1220–1290 CE]
-
A.
occupationPeriod
chosen
Indicates the time span during which an entity holds or held a particular occupation or role.
-
B.
historicalPeriodOfMajorActivity
Indicates the historical period during which an entity carried out its most significant or influential activities.
-
C.
flourishedDuring
Indicates that an entity was active, thriving, or at its peak during a specified time period or era.
-
D.
historicalPeriodOfSignificance
Indicates the time period during which an entity is considered to have had its most important or influential historical impact.
-
E.
notableOccupationContext
Indicates that the referenced occupation is notable or significant specifically within the given contextual framework or domain.
- 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_69a494267b4c819088c97a59182bf56a |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd35fb888190adf1e5d0615fa725 |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb59ca6c81908597a81646674aaa |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.