Triple
T19827105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koinonia Farm |
E476354
|
entity |
| Predicate | historicalPeriodOfPersecution |
P4706
|
FINISHED |
| Object | 1950s |
—
|
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: 1950s | Statement: [Koinonia Farm, historicalPeriodOfPersecution, 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPeriodOfPersecution Context triple: [Koinonia Farm, historicalPeriodOfPersecution, 1950s]
-
A.
persecutionHistory
Indicates that an entity has experienced, participated in, or is otherwise associated with acts of persecution in the past.
-
B.
persecutedDuring
chosen
Indicates that one entity systematically harassed, oppressed, or victimized another entity during a specified time period or event.
-
C.
methodOfPersecution
Indicates the specific means, technique, or process by which an act of persecution is carried out.
-
D.
persecutionOf
Indicates the act of subjecting an entity to persistent, often unjust hostility, harassment, or oppression, typically on the basis of identity, beliefs, or group membership.
-
E.
persecutionBegan
Indicates that the act or process of persecuting a target started at a specific point in time.
- 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e656cb20788190b9deac6b8af6a55d |
completed | April 20, 2026, 4:39 p.m. |
| PD | Predicate disambiguation | batch_69e5305bda388190a23b7191768107b1 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.