Triple
T9791533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USSF enlisted rank structure |
E237617
|
entity |
| Predicate | E-3RankTitle |
P19071
|
FINISHED |
| Object | Specialist 3 |
—
|
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: Specialist 3 | Statement: [USSF enlisted rank structure, E-3RankTitle, Specialist 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: E-3RankTitle Context triple: [USSF enlisted rank structure, E-3RankTitle, Specialist 3]
-
A.
namedForRank
Indicates that something is named after a specific rank or title held by an entity.
-
B.
officeHolderRankSometimes
Indicates that an office holder’s rank or level within a position can vary or apply only in certain situations or periods.
-
C.
legalHierarchyRank
Indicates the relative position or level of authority an entity holds within a legal or judicial hierarchy.
-
D.
recruitingRanking
Indicates the relative standing or quality level assigned to an entity based on its effectiveness or success in recruiting participants, members, or talent.
-
E.
rankEquivalent
chosen
Indicates that two entities hold the same rank or hierarchical level within a given ordering or 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_69ca84dc04488190b9c91193976c0960 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda3456bac819097afb20ce9081dd7 |
completed | April 1, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69cd03da45a88190b71b1be3354c15a6 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:28 p.m.