Triple
T26801987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Director of the FSB |
E671125
|
entity |
| Predicate | hasRankTraditionally |
P7007
|
FINISHED |
| Object | general officer rank |
—
|
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: general officer rank | Statement: [Director of the FSB, hasRankTraditionally, general officer rank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRankTraditionally Context triple: [Director of the FSB, hasRankTraditionally, general officer rank]
-
A.
hasRanks
Indicates that one entity possesses, is assigned, or is associated with one or more rank levels or hierarchical positions.
-
B.
hasRankCategory
Indicates that an entity is assigned to a particular rank-based classification or level within an ordered hierarchy.
-
C.
containsRank
Indicates that one entity includes or encompasses another entity that has a specific rank or hierarchical level within it.
-
D.
typicallyHoldsRank
chosen
Indicates that an entity is most commonly or usually associated with holding a particular rank or level in a hierarchy.
-
E.
hasRankingUnit
Indicates that one entity is associated with a specific unit or scale used to express its ranking or ordered position.
- 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_69eeb31fbd888190a82dac5822e453bc |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 27, 2026, 4:23 a.m.