Triple
T21154572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Space Force officers |
E521278
|
entity |
| Predicate | useRankTitles |
P143087
|
FINISHED |
| Object | second lieutenant |
—
|
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: second lieutenant | Statement: [United States Space Force officers, useRankTitles, second lieutenant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: useRankTitles Context triple: [United States Space Force officers, useRankTitles, second lieutenant]
-
A.
hasRankOrTitle
Indicates that an entity holds, is assigned, or is associated with a specific rank, title, or formal designation.
-
B.
lowerOrEqualRankTitle
Indicates that one entity’s rank or title is lower than or equal to the rank or title of another entity.
-
C.
namedForRank
Indicates that something is named after a specific rank or title held by an entity.
-
D.
nobleRankType
Indicates the specific category or level of nobility associated with an entity within a hierarchical noble rank system.
-
E.
nobleRankInOrder
Indicates that an entity holds a specific noble rank at a particular position within an established order of nobility.
- 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_69e0b50d1ea481909c07e63c3ead9316 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7252a48788190bfdfe811fc6cfc06 |
completed | April 21, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 2:58 p.m.