Triple
T33400223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Van resistance of 1915 |
E855274
|
entity |
| Predicate | opposingEthnicGroup |
P72540
|
FINISHED |
| Object | Ottoman Turks |
—
|
NE NERFINISHED |
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: Ottoman Turks | Statement: [Van resistance of 1915, opposingEthnicGroup, Ottoman Turks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposingEthnicGroup Context triple: [Van resistance of 1915, opposingEthnicGroup, Ottoman Turks]
-
A.
mainOppositionEthnicGroup
Indicates that the subject’s primary opposing group in a conflict or rivalry is characterized by a particular ethnic identity.
-
B.
otherEthnicGroup
Indicates that one entity belongs to a different ethnic group than the other entity.
-
C.
ethnicGroupConfronted
chosen
Indicates that one ethnic group has faced opposition, conflict, or hostile interaction from another group or entity.
-
D.
affectedEthnicGroup
Indicates that a particular ethnic group is impacted or influenced by an event, condition, policy, or action.
-
E.
involvedEthnicGroup
Indicates that a particular ethnic group participates in, is affected by, or is otherwise associated with the referenced event, situation, or 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_69f3496e3f1c8190bcecfa82aa9d17ff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: May 1, 2026, 1:35 a.m.