Triple
T7757744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jemmy |
E175939
|
entity |
| Predicate | ledUprisingAgainst |
P45578
|
FINISHED |
| Object | British colonial authorities in South Carolina |
—
|
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: British colonial authorities in South Carolina | Statement: [Jemmy, ledUprisingAgainst, British colonial authorities in South Carolina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ledUprisingAgainst Context triple: [Jemmy, ledUprisingAgainst, British colonial authorities in South Carolina]
-
A.
uprising
Indicates a collective act of resistance or rebellion by a group against an established authority or ruling power.
-
B.
resultOfUprising
Indicates that something exists or occurs as a consequence or outcome of an uprising or rebellion.
-
C.
hasCenterOfUprising
Indicates that a location serves as the main focal point or hub where an uprising or rebellion is centered or originates.
-
D.
uprisingDate
Indicates the date on which an uprising or rebellion occurred or began.
-
E.
facedRebellionBy
chosen
Indicates that an entity experienced opposition or an uprising initiated by another 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_69c6996180088190832e38e8d83ff54a |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c705257ca08190a78c592a1e616da8 |
completed | March 27, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69c7016df2b08190b2330a2010691431 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:09 p.m.