Triple
T27028713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Navy personnel |
E680856
|
entity |
| Predicate | typicalEnlistedPrefix |
P199806
|
FINISHED |
| Object | E |
—
|
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 | Statement: [U.S. Navy personnel, typicalEnlistedPrefix, E]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEnlistedPrefix Context triple: [U.S. Navy personnel, typicalEnlistedPrefix, E]
-
A.
militaryRankTypicallyHeldBy
Indicates that a given military rank is most commonly or usually held by a particular type or category of person or position.
-
B.
namedForMilitaryRank
Indicates that one entity is named after or in honor of a specific military rank held by a person or associated with a military position.
-
C.
usesMilitaryRanks
Indicates that a system, organization, or context employs formal military rank titles to define roles, hierarchy, or status among its members.
-
D.
isMilitaryRank
Indicates that one entity holds a specific position or level within a formal military hierarchy in relation to another.
-
E.
militaryRank
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
- 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_69eeeb5566f08190813daf896fa3da04 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69ff59b33a38819086cc9aa19b81748b |
completed | May 9, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69ff587758f88190a39c2164341dc554 |
completed | May 9, 2026, 3:53 p.m. |
| PDg | Predicate description generation | batch_69ff59b1e2ac8190bb65529e9dbbb178 |
completed | May 9, 2026, 3:58 p.m. |
Created at: April 27, 2026, 7:12 a.m.