Triple
T17231566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 89th Airlift Wing commander |
E418252
|
entity |
| Predicate | typicallyHoldsRankAtLeast |
P7007
|
FINISHED |
| Object | colonel (O-6) |
—
|
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: colonel (O-6) | Statement: [89th Airlift Wing commander, typicallyHoldsRankAtLeast, colonel (O-6)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyHoldsRankAtLeast Context triple: [89th Airlift Wing commander, typicallyHoldsRankAtLeast, colonel (O-6)]
-
A.
typicallyHoldsRank
chosen
Indicates that an entity is most commonly or usually associated with holding a particular rank or level in a hierarchy.
-
B.
containsRank
Indicates that one entity includes or encompasses another entity that has a specific rank or hierarchical level within it.
-
C.
hasRankOrTitle
Indicates that an entity holds, is assigned, or is associated with a specific rank, title, or formal designation.
-
D.
eligibleRank
Indicates that an entity meets the required rank or level criteria to qualify for a specific role, action, or benefit.
-
E.
rankRestriction
Indicates a constraint or limit placed on the rank or hierarchical level that an entity may hold within a given system or structure.
- 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42df7da748190a3a1762a67eb871b |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.