Triple
T5053805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Company Commander |
E113849
|
entity |
| Predicate | hasRankType |
P11443
|
FINISHED |
| Object | commissioned officer |
—
|
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: commissioned officer | Statement: [Company Commander, hasRankType, commissioned officer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRankType Context triple: [Company Commander, hasRankType, commissioned officer]
-
A.
hasRankCategory
chosen
Indicates that an entity is assigned to a particular rank-based classification or level within an ordered hierarchy.
-
B.
hasRankContext
Indicates that an entity’s rank or ordering is defined, interpreted, or constrained within a specific contextual framework or situation.
-
C.
hasRankVariant
Indicates that one entity is an alternative or variant form of another entity’s rank or hierarchical level.
-
D.
isRank
Indicates that one entity serves as the rank, level, or hierarchical position associated with another entity.
-
E.
hasRankingCategory
Indicates that an entity is associated with a particular ranking category or tier within an ordered classification system.
- 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_69bd443aa1f88190abb992d138f2cf42 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd742a59448190918766c261cfa13d |
completed | March 20, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69bd715479f08190933604aebd34414f |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:38 p.m.