Triple
T8717507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O-10 |
E206931
|
entity |
| Predicate | isAboveEnlistedGrade |
P84085
|
FINISHED |
| Object | E-9 |
—
|
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: E-9 | Statement: [O-10, isAboveEnlistedGrade, E-9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAboveEnlistedGrade Context triple: [O-10, isAboveEnlistedGrade, E-9]
-
A.
militaryRankEligibility
Indicates that one entity is qualified or permitted to hold, attain, or be considered for a specified military rank.
-
B.
isMilitaryOrderGrade
Indicates that one entity is classified as a specific grade or level within a military order or honor system in relation to another entity.
-
C.
isCivilianHonourGrade
Indicates that one entity is classified as a specific grade or level within a system of civilian honours or awards in relation to another entity.
-
D.
hasCommanderRank
Indicates that an entity holds the military or organizational rank of commander within a specified hierarchy or context.
-
E.
isMilitaryRank
Indicates that one entity holds a specific position or level within a formal military hierarchy in relation to another.
- 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_69ca83572d4881909bef3be2b578d539 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5cdac6988190b9f9cc1f350aae53 |
completed | March 31, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69cc456e806c819087e7d66ee737f242 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc46c40c54819093d174a4203f9515 |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:36 p.m.