Triple
T29750115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French military hierarchy |
E752869
|
entity |
| Predicate | highestOfficerRank |
P4202
|
FINISHED |
| Object | Général d’armée |
—
|
NE NERFINISHED |
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: Général d’armée | Statement: [French military hierarchy, highestOfficerRank, Général d’armée]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestOfficerRank Context triple: [French military hierarchy, highestOfficerRank, Général d’armée]
-
A.
isHighestRankedUniformedOfficerIn
Indicates that one entity holds the top-ranking position among all uniformed officers within a specified organization or jurisdiction.
-
B.
seniorOfficerRank
Indicates that one entity holds a higher or more senior officer rank than the other within a hierarchical structure.
-
C.
highestNonCommissionedRank
Indicates that the subject holds the top position among all non-commissioned ranks within a given hierarchy or organization.
-
D.
highestRankIn
chosen
Indicates that one entity holds the top or most senior rank within a specified group, category, or context relative to other entities.
-
E.
hasGeneralOfficerRank
Indicates that an entity holds a military rank at the general officer 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_69f0d62c84cc8190846f80ae04fdf8ec |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 28, 2026, 7:53 p.m.