Triple
T34189922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pasha Antipov |
E877071
|
entity |
| Predicate | militaryAlias |
P190082
|
FINISHED |
| Object | Strelnikov |
—
|
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: Strelnikov | Statement: [Pasha Antipov, militaryAlias, Strelnikov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryAlias Context triple: [Pasha Antipov, militaryAlias, Strelnikov]
-
A.
militaryBranchAbbreviation
Indicates the standard shortened form or acronym used to represent a specific branch of a military organization.
-
B.
usesMilitaryRanks
Indicates that a system, organization, or context employs formal military rank titles to define roles, hierarchy, or status among its members.
-
C.
hasMilitaryDesignation
Indicates that an entity is assigned a specific military-related code, title, or classification.
-
D.
militaryBranchAssociatedWith
Indicates a relationship where an entity is connected to, or operates as part of, a specific branch of a military organization.
-
E.
troopsColloquiallyKnownAs
Indicates that a group of troops is commonly referred to by a particular informal or colloquial name.
- F. None of above. chosen
Provenance (4 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_69f349af20a4819089ac24d28f2d8112 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69fcab6d41a88190a3576b4b088dcabd |
completed | May 7, 2026, 3:10 p.m. |
Created at: May 1, 2026, 1:55 a.m.