Triple
T17108449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Officer Commanding‑in‑Chief, South Western Command |
E415159
|
entity |
| Predicate | insigniaRank |
P84082
|
FINISHED |
| Object | three‑star 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: three‑star general | Statement: [General Officer Commanding‑in‑Chief, South Western Command, insigniaRank, three‑star general]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: insigniaRank Context triple: [General Officer Commanding‑in‑Chief, South Western Command, insigniaRank, three‑star general]
-
A.
rankInsigniaDescription
Indicates the descriptive text that explains the appearance or characteristics of a rank insignia associated with an entity.
-
B.
rankGrade
Indicates the grade or level assigned to an entity within a ranking or evaluation system.
-
C.
isRank
Indicates that one entity serves as the rank, level, or hierarchical position associated with another entity.
-
D.
rankTier
Indicates the classification level or tier assigned to an entity within a ranking or hierarchical system.
-
E.
rankInsigniaStars
chosen
Indicates the number or configuration of stars displayed on a rank insignia to denote a specific rank or level.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dc2906a081909d0d43cf04319f52 |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d6b1b988190a8d6b6fe78c35e59 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.