Triple
T26391803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet Guards units |
E663430
|
entity |
| Predicate | hadPriorityForReplacements |
P160590
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Soviet Guards units, hadPriorityForReplacements, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadPriorityForReplacements Context triple: [Soviet Guards units, hadPriorityForReplacements, yes]
-
A.
hasReplaced
Indicates that one entity has taken the place or function of another entity, superseding it in a given context.
-
B.
hasPriorityAt
Indicates that one entity holds a specified level of priority or precedence at a particular time, place, or context relative to others.
-
C.
hadPriorityForEquipment
Indicates that one entity was given precedence or preferential access over others in obtaining or using a particular piece of equipment.
-
D.
seeksToReplace
Indicates an intention or effort by one entity to take over the role, function, or position currently held by another entity.
-
E.
primaryReplacementFor
Indicates that one entity serves as the main or preferred substitute or successor for another entity.
- 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610c024f081908237794984538566 |
completed | May 2, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f6037bf7a081908862a8359be80cf8 |
completed | May 2, 2026, 2 p.m. |
Created at: April 26, 2026, 11:26 p.m.