Triple
T1925961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Loyalists |
E40831
|
entity |
| Predicate | causeOfPersecution |
P33526
|
FINISHED |
| Object | allegiance to Britain |
—
|
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: allegiance to Britain | Statement: [American Loyalists, causeOfPersecution, allegiance to Britain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfPersecution Context triple: [American Loyalists, causeOfPersecution, allegiance to Britain]
-
A.
persecutedDuring
Indicates that one entity systematically harassed, oppressed, or victimized another entity during a specified time period or event.
-
B.
methodOfPersecution
Indicates the specific means, technique, or process by which an act of persecution is carried out.
-
C.
ethnicGroupPersecuted
Indicates that a particular ethnic group is subjected to systematic hostility, discrimination, or violence by another party.
-
D.
persecutionHistory
Indicates that an entity has experienced, participated in, or is otherwise associated with acts of persecution in the past.
-
E.
causeOfExile
Indicates the reason or circumstance that led to an entity’s exile.
- 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_69a8864711648190b07bed24ed76258e |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb261ef8481909be2390ac5a02622 |
completed | March 7, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_69abafeec6f881909d47acb966683279 |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb20c4970819086e66a5435744297 |
completed | March 7, 2026, 5:05 a.m. |
Created at: March 4, 2026, 7:35 p.m.