Triple
T34444680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Hare (historic fort) |
E884192
|
entity |
| Predicate | opposedGroups |
P116577
|
FINISHED |
| Object | Xhosa groups |
—
|
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: Xhosa groups | Statement: [Fort Hare (historic fort), opposedGroups, Xhosa groups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposedGroups Context triple: [Fort Hare (historic fort), opposedGroups, Xhosa groups]
-
A.
opposedByGroup
Indicates that an action, proposal, or entity is met with opposition or resistance from a particular group.
-
B.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
C.
opponentGroup
chosen
Indicates that one group is in opposition or conflict with another group, typically as a rival, competitor, or adversary.
-
D.
isOppositionGroup
Indicates that one group stands in organized resistance or conflict against another group, authority, policy, or system.
-
E.
opposesClass
Indicates a relationship where one entity actively resists, challenges, or works against the interests, actions, or status of a particular social or economic class.
- 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_69f349c548d88190978e2a82502c03d0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: May 1, 2026, 2 a.m.