Triple
T25160749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jenderal Besar |
E626431
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | honorary military rank |
C22688
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: honorary military rank Context triple: [Jenderal Besar, instanceOf, honorary military rank]
-
A.
military honorific designation
A military honorific designation is a formal title or label conferred upon individuals, units, or formations to recognize distinguished service, valor, heritage, or special status within the armed forces.
-
B.
military-equivalent rank
A military-equivalent rank is a formal position or title in a non-military organization that is defined to correspond in status, authority, or protocol to a specific rank within a military hierarchy.
-
C.
honorary status
chosen
Honorary status is a formally recognized, typically non-remunerative distinction granted to an individual as a mark of respect, achievement, or contribution, without conferring the full rights or responsibilities of a regular position.
-
D.
historical military rank
A historical military rank is a formally defined level of authority and responsibility within past armed forces, reflecting the hierarchical structure, duties, and social status of military personnel in a specific historical context.
-
E.
honorary order
An honorary order is a formal system of titles, decorations, or memberships conferred by a state or organization to recognize individuals for distinguished service, achievement, or merit.
- F. None of above.
Provenance (1 batch)
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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:31 a.m.