Triple
T923038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ottoman dynasty |
E19923
|
entity |
| Predicate | usedPractice |
P12146
|
FINISHED |
| Object | fratricide (historically) |
—
|
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: fratricide (historically) | Statement: [Ottoman dynasty, usedPractice, fratricide (historically)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedPractice Context triple: [Ottoman dynasty, usedPractice, fratricide (historically)]
-
A.
typicalPractice
chosen
Indicates that an action, behavior, or method is commonly or customarily done in a given context or by a given group.
-
B.
stillPracticedIn
Indicates that a tradition, custom, or practice continues to be actively carried out or observed in a specified place or context.
-
C.
usedDuring
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
-
D.
isPracticedBy
Indicates that an activity, skill, or discipline is regularly performed or carried out by a particular entity.
-
E.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
- 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_69a493a099788190a696d9d8408cbaf4 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b314f6fc81908a3ccc2e741e3c2b |
completed | March 1, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69a4b295b02481908e5f53bfcb83cc94 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.