Triple
T29750119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French military hierarchy |
E752869
|
entity |
| Predicate | highestGendarmerieRank |
P180796
|
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, highestGendarmerieRank, Général d’armée]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestGendarmerieRank Context triple: [French military hierarchy, highestGendarmerieRank, Général d’armée]
-
A.
isGendarmerieType
Indicates that an entity belongs to, or is classified as, a specific type or category within the gendarmerie (military police) organization.
-
B.
highestNonCommissionedRank
Indicates that the subject holds the top position among all non-commissioned ranks within a given hierarchy or organization.
-
C.
seniorOfficerRank
Indicates that one entity holds a higher or more senior officer rank than the other within a hierarchical structure.
-
D.
militaryRank
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
-
E.
hasGeneralOfficerRank
Indicates that an entity holds a military rank at the general officer level.
- 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_69f0d62c84cc8190846f80ae04fdf8ec |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
| PDg | Predicate description generation | batch_69f7516c538481908c6e55cf76add098 |
completed | May 3, 2026, 1:45 p.m. |
Created at: April 28, 2026, 7:53 p.m.