Triple
T32311221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Negro Fort |
E825504
|
entity |
| Predicate | reasonForThreat |
P192582
|
FINISHED |
| Object | encouragement of slave escapes |
—
|
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: encouragement of slave escapes | Statement: [Negro Fort, reasonForThreat, encouragement of slave escapes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForThreat Context triple: [Negro Fort, reasonForThreat, encouragement of slave escapes]
-
A.
reasonForAttack
Indicates that one entity’s attack on another is motivated or caused by the specified reason.
-
B.
protectionReason
Indicates the justification or cause for which protection is provided or required in the relationship between entities.
-
C.
reasonForBan
Indicates the justification or cause that led to an entity being banned.
-
D.
reasonForSuppression
Indicates the justification or cause for which something (such as information, data, or content) has been withheld, hidden, or prevented from being shown or used.
-
E.
reasonForDangerListing
Indicates the specific cause or justification for why something has been classified or listed as dangerous.
- F. None of above. chosen
Provenance (4 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
| PDg | Predicate description generation | batch_69fd19f6a7888190aa7eee2b87687c53 |
completed | May 7, 2026, 11:02 p.m. |
Created at: May 1, 2026, 12:46 a.m.