Triple
T29750138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French military hierarchy |
E752869
|
entity |
| Predicate | typicalEnlistedGrade |
P203916
|
FINISHED |
| Object | Caporal-chef |
—
|
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: Caporal-chef | Statement: [French military hierarchy, typicalEnlistedGrade, Caporal-chef]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEnlistedGrade Context triple: [French military hierarchy, typicalEnlistedGrade, Caporal-chef]
-
A.
typicalEnlistedPrefix
Indicates that one entity is the standard or commonly used prefix associated with an enlisted rank or enlisted designation of another entity.
-
B.
officerGrade
Indicates the rank or grade level assigned to an officer within an organizational or military hierarchy.
-
C.
militaryRankTypicallyHeldBy
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.
militaryRankEligibility
Indicates that one entity is qualified or permitted to hold, attain, or be considered for a specified military rank.
- 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_6a02f10505988190be5fd57566a90e0f |
completed | May 12, 2026, 9:21 a.m. |
| PD | Predicate disambiguation | batch_6a02f03a8c1481909e137e270119f7ef |
completed | May 12, 2026, 9:17 a.m. |
| PDg | Predicate description generation | batch_6a02f10460a881909ed6a7159ecf1e84 |
completed | May 12, 2026, 9:21 a.m. |
Created at: April 28, 2026, 7:53 p.m.