Triple
T16719386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ensign (United States Navy) |
E406305
|
entity |
| Predicate | isLowestCommissionedRank |
P112047
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ensign (United States Navy), isLowestCommissionedRank, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLowestCommissionedRank Context triple: [Ensign (United States Navy), isLowestCommissionedRank, true]
-
A.
lowestCommissionedRank
chosen
Indicates that the subject holds the lowest commissioned rank within a specified hierarchy or organization.
-
B.
isAboveEnlistedGrade
Indicates that one entity holds a military rank or grade that is higher than the enlisted level of another entity.
-
C.
isCommissionedRankAbbreviation
Indicates that one term is an abbreviation for a commissioned military rank represented by the other term.
-
D.
militaryRankEligibility
Indicates that one entity is qualified or permitted to hold, attain, or be considered for a specified military rank.
-
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.
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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3865855108190bf8767b7b6c5fa10 |
completed | April 18, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.