Triple
T12924899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W-1 |
E309217
|
entity |
| Predicate | rankGroupOrder |
P17947
|
FINISHED |
| Object | lowest warrant officer grade in the U.S. Navy |
—
|
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: lowest warrant officer grade in the U.S. Navy | Statement: [W-1, rankGroupOrder, lowest warrant officer grade in the U.S. Navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankGroupOrder Context triple: [W-1, rankGroupOrder, lowest warrant officer grade in the U.S. Navy]
-
A.
rankOverField
Indicates that one entity’s rank or ordering is determined relative to another entity within a specified field or domain.
-
B.
rankType
Indicates the specific category or classification of a rank within a ranking or hierarchy system.
-
C.
hasRankOrder
chosen
Indicates that one entity is ordered or positioned relative to others according to a specific ranking or sequence.
-
D.
rankEquivalent
Indicates that two entities hold the same rank or hierarchical level within a given ordering or classification system.
-
E.
rankStyle
Indicates the manner or criteria by which items are ordered or prioritized relative to one 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971e9576c81908eb59569af6da877 |
completed | April 10, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69d96fab4d0881909a7a4d66bab9aa85 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:42 p.m.