Triple
T301313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian State Military Archive |
E6202
|
entity |
| Predicate | userGroup |
P1846
|
FINISHED |
| Object | historians |
—
|
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: historians | Statement: [Russian State Military Archive, userGroup, historians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: userGroup Context triple: [Russian State Military Archive, userGroup, historians]
-
A.
hasUserGroup
chosen
Indicates that a user is associated with, belongs to, or is a member of a specific user group.
-
B.
userBase
Indicates that one entity serves as the primary or foundational group of users associated with another entity.
-
C.
memberOf
Indicates that an entity belongs to, is part of, or is a constituent of a larger group, organization, or collection.
-
D.
user
Indicates a relationship where an entity actively operates, controls, or interacts with another entity, typically as the primary agent or consumer of its function.
-
E.
hasSupporterGroup
Indicates that an entity is associated with a group of supporters that backs, promotes, or advocates for it.
- 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_69a2e79230508190b912ecb555aae17e |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea2fba548190a5aeb1597dca96bd |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e93aff048190a633c8ae2b76a41f |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.