Triple
T18406852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People's Liberation Army rank system |
E441645
|
entity |
| Predicate | hasNCOGrade |
P131503
|
FINISHED |
| Object | Corporal |
—
|
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: Corporal | Statement: [People's Liberation Army rank system, hasNCOGrade, Corporal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNCOGrade Context triple: [People's Liberation Army rank system, hasNCOGrade, Corporal]
-
A.
hasGradeStatus
Indicates that an entity holds a particular grade-related status or standing within an evaluation or grading system.
-
B.
hasSeniorNCO
Indicates that an entity has, is assigned, or is associated with a senior non-commissioned officer in a supervisory or leadership capacity.
-
C.
hasCadetRank
Indicates that an entity holds or is assigned a cadet-level rank within a hierarchical or military-style ranking system.
-
D.
hasGrades
Indicates that an entity possesses or is associated with one or more grade values, typically reflecting evaluations or scores.
-
E.
hasGradeCount
Indicates a relationship where an entity is associated with the number of grades it has or has received.
- 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_69d8b9eb8a508190a942fd75ebd8b1dc |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e519591fdc8190a92f9587ec88478d |
completed | April 19, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e469bf7f74819096a01173493412c2 |
completed | April 19, 2026, 5:35 a.m. |
| PDg | Predicate description generation | batch_69e46d2aa72c8190a40854a7a52081e2 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 10:46 a.m.