Triple
T11734174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eighth Frontier War |
E278982
|
entity |
| Predicate | hasBroaderTopic |
P24066
|
FINISHED |
| Object | colonial expansion in Southern Africa |
—
|
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: colonial expansion in Southern Africa | Statement: [Eighth Frontier War, hasBroaderTopic, colonial expansion in Southern Africa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBroaderTopic Context triple: [Eighth Frontier War, hasBroaderTopic, colonial expansion in Southern Africa]
-
A.
hasSubConcept
Indicates that one concept is a more specific, subordinate, or narrower idea within the scope of another, more general concept.
-
B.
hasSubdiscipline
Indicates that one discipline includes another, more specialized field of study as a subordinate branch.
-
C.
hasPrimarySubject
Indicates that an entity is the main or principal subject associated with another entity or resource.
-
D.
broaderProcess
Indicates that one process encompasses, includes, or provides the larger context for another, more specific process.
-
E.
includesTopics
chosen
Indicates that one entity contains, covers, or addresses the specified topics as part of its content or scope.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4daa7f48190896fc7653e9dd70b |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.