Triple
T37389224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Afrikaans literature |
E928657
|
entity |
| Predicate | sawMajorGrowthInCentury |
P186852
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Afrikaans literature, sawMajorGrowthInCentury, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sawMajorGrowthInCentury Context triple: [Afrikaans literature, sawMajorGrowthInCentury, 20th century]
-
A.
experiencedRapidGrowthInCentury
Indicates that the entity underwent a significant and swift increase or expansion during the specified century.
-
B.
sawMajorGrowthIn
chosen
Indicates that an entity experienced a significant increase or expansion in something (such as size, value, or activity) during a specified period or context.
-
C.
developedFurtherInCentury
Indicates that something was expanded, advanced, or more fully developed during the specified century.
-
D.
happenedInCentury
Indicates that an event or occurrence took place during a specified century.
-
E.
collapseCentury
Indicates that one time period or event causes or undergoes a breakdown or compression of its century-level temporal distinction, effectively merging or reducing it into a different or broader timeframe.
- 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_69f76ebb10c481909b54b9dba263e29f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.