Triple
T28450968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ottoman-Crimean alliance |
E716577
|
entity |
| Predicate | militaryRoleOfCrimea |
P9463
|
FINISHED |
| Object | provider of light cavalry |
—
|
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: provider of light cavalry | Statement: [Ottoman-Crimean alliance, militaryRoleOfCrimea, provider of light cavalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryRoleOfCrimea Context triple: [Ottoman-Crimean alliance, militaryRoleOfCrimea, provider of light cavalry]
-
A.
militaryRole
chosen
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
B.
militaryFunction
Indicates a relationship where an entity serves a specific role, duty, or operational purpose within a military context.
-
C.
roleDuringRussianCivilWar
Indicates the specific function, position, or involvement an entity had during the period of the Russian Civil War.
-
D.
roleInWarOrConflict
Indicates the specific function, position, or involvement an entity has within a particular war or conflict.
-
E.
roleInRussia
Indicates that an entity holds or has held an official or notable role, position, or function within the context of Russia.
- 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_69efd6b76f8c8190a7ba908aca280942 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 28, 2026, 1:51 a.m.