Triple
T715714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adjarians |
E14308
|
entity |
| Predicate | historicalProcess |
P11492
|
FINISHED |
| Object | Islamization under Ottoman rule |
—
|
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: Islamization under Ottoman rule | Statement: [Adjarians, historicalProcess, Islamization under Ottoman rule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalProcess Context triple: [Adjarians, historicalProcess, Islamization under Ottoman rule]
-
A.
majorHistoricalProcess
chosen
Indicates a large-scale, transformative sequence of events or developments that significantly shapes the course of history.
-
B.
historicalFunction
Indicates the role, purpose, or activity an entity had during a past period or in a historical context.
-
C.
historicalMethod
Indicates that a particular method, approach, or technique was used in the past, typically in a historical context or during a previous period of activity.
-
D.
historicalForm
Indicates that one entity is an earlier or historically attested form or variant of another entity.
-
E.
administrativeHistory
Indicates the sequence of past administrative changes, statuses, or governing arrangements that have affected an entity over 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_69a4934a36e081909e7abef98b898a4e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a574b4d881908b6d0be386081efd |
completed | March 1, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f38898819089d79bad4f4ff2d2 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.