Triple
T29750125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French military hierarchy |
E752869
|
entity |
| Predicate | typicalGeneralOfficerRank |
P181774
|
FINISHED |
| Object | Général de brigade |
—
|
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: Général de brigade | Statement: [French military hierarchy, typicalGeneralOfficerRank, Général de brigade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGeneralOfficerRank Context triple: [French military hierarchy, typicalGeneralOfficerRank, Général de brigade]
-
A.
hasGeneralOfficerRank
Indicates that an entity holds a military rank at the general officer level.
-
B.
commandingOfficerRank
Indicates the military rank held by the officer who has command authority over a given individual or unit.
-
C.
militaryRankTypicallyHeldBy
chosen
Indicates that a given military rank is most commonly or usually held by a particular type or category of person or position.
-
D.
militaryRank
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
-
E.
officerGrade
Indicates the rank or grade level assigned to an officer within an organizational or military hierarchy.
- 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_6a0245e917748190bf0a65db538aa66f |
completed | May 11, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_6a023f7cf7148190af5c2ea501511145 |
completed | May 11, 2026, 8:43 p.m. |
Created at: April 28, 2026, 7:53 p.m.