Triple
T22895351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Wales’s Own |
E568158
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military honorific |
C22229
|
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: military honorific Context triple: [Prince of Wales’s Own, instanceOf, military honorific]
-
A.
military honorific designation
chosen
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 honour
Military honour is the socially and institutionally recognized esteem accorded to individuals or groups for exemplary conduct, bravery, or service within a military context, reflecting adherence to martial values and codes of ethics.
-
C.
dignité militaire
Dignité militaire désigne le statut honorifique et symbolique conféré à une personne ou à une institution en reconnaissance de son rang, de ses mérites ou de ses services rendus dans le domaine militaire, indépendamment de fonctions opérationnelles effectives.
-
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.
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.
- 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_69e2458c23ec81908fa2570692c6614f |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:40 p.m.