Triple
T16142875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sacking of Lawrence |
E391705
|
entity |
| Predicate | ideologyOfAttackers |
P65775
|
FINISHED |
| Object | pro-slavery |
—
|
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: pro-slavery | Statement: [Sacking of Lawrence, ideologyOfAttackers, pro-slavery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ideologyOfAttackers Context triple: [Sacking of Lawrence, ideologyOfAttackers, pro-slavery]
-
A.
ideologyOfInsurgents
Indicates the guiding beliefs, values, or political doctrine held by insurgent groups that shape their goals and actions.
-
B.
ideologyOfPerpetrators
chosen
Indicates the shared ideological beliefs or motivations held by the individuals or groups who carried out the act or offense.
-
C.
opposingFactionIdeology
Indicates that two factions hold ideologies that are in direct conflict or fundamental opposition to each other.
-
D.
belligerentIdeology
Indicates that an ideology promotes, endorses, or is fundamentally oriented toward aggression, conflict, or hostile action.
-
E.
opposingIdeology
Indicates that two entities hold conflicting or mutually incompatible belief systems, doctrines, or ideological positions.
- 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21d9082588190bc7e6ff491f0d94e |
completed | April 17, 2026, 11:46 a.m. |
| PD | Predicate disambiguation | batch_69e182885bc08190822ae7e8a4b8ac1f |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.