Triple
T1949008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vice Chairman of the Central Military Commission |
E42117
|
entity |
| Predicate | typicallyHeldRank |
P7007
|
FINISHED |
| Object | general |
—
|
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 | Statement: [Vice Chairman of the Central Military Commission, typicallyHeldRank, general]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyHeldRank Context triple: [Vice Chairman of the Central Military Commission, typicallyHeldRank, general]
-
A.
typicallyHoldsRank
chosen
Indicates that an entity is most commonly or usually associated with holding a particular rank or level in a hierarchy.
-
B.
eligibleRank
Indicates that an entity meets the required rank or level criteria to qualify for a specific role, action, or benefit.
-
C.
rankHeldByPost
Indicates that a particular organizational post or position is associated with, or carries, a specific rank.
-
D.
seniorRank
Indicates that one entity holds a higher or more senior rank or position than another entity.
-
E.
highestRankIn
Indicates that one entity holds the top or most senior rank within a specified group, category, or context relative to other entities.
- 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_69a8870e08fc8190a319cbf2600db15f |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3315df481908f60cd87453fbc03 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abaff25a588190bb4cbc8df9fc6d64 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.