Triple
T14844223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Page Corps (Imperial Russia) |
E349043
|
entity |
| Predicate | producedRank |
P116050
|
FINISHED |
| Object | officers of the Imperial Guard |
—
|
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: officers of the Imperial Guard | Statement: [Page Corps (Imperial Russia), producedRank, officers of the Imperial Guard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producedRank Context triple: [Page Corps (Imperial Russia), producedRank, officers of the Imperial Guard]
-
A.
rankedBy
Indicates that one entity is ordered or assigned a position in a hierarchy or list according to criteria determined or applied by another entity.
-
B.
rankedAs
Indicates that one entity is assigned a specific position or level in an ordered ranking relative to others.
-
C.
representsRank
Indicates that one entity serves as the rank, status, or hierarchical level assigned to another entity.
-
D.
isRanked
Indicates that an entity has been assigned a position or level within an ordered hierarchy or comparative list.
-
E.
peakOutputRanking
Indicates the relative position of an entity in an ordered list based on its maximum or peak output level.
- 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_69d822ec69008190a9232caa68836872 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded291103c8190a64cfe700bfee197 |
completed | April 14, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69de8c13418c819088ff9905ace1416a |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de90806f3881908fcbfec5bd4ab4d2 |
completed | April 14, 2026, 7:07 p.m. |
Created at: April 10, 2026, 1:53 a.m.