Triple
T27028715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Navy personnel |
E680856
|
entity |
| Predicate | typicalWarrantPrefix |
P199852
|
FINISHED |
| Object | W |
—
|
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: W | Statement: [U.S. Navy personnel, typicalWarrantPrefix, W]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalWarrantPrefix Context triple: [U.S. Navy personnel, typicalWarrantPrefix, W]
-
A.
typicalKey
Indicates that the referenced key is the standard or most commonly used key associated with an entity or context.
-
B.
typicalTerm
Indicates that something is a standard, representative, or characteristic term typically associated with a given concept or context.
-
C.
isTypicallyGrantedTo
Indicates that something is customarily or usually given, awarded, or allowed to a particular recipient or group.
-
D.
typicalRights
Indicates that one entity normally or customarily has certain rights or entitlements in relation to another entity or context.
-
E.
typicalPrecedent
Indicates that one situation, case, or event serves as a standard or commonly followed example for how similar later situations are handled.
- 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_69ff5f5ecc808190b2df364da108ff4c |
completed | May 9, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69ff5b84131c8190bf81d7fb53e934bc |
completed | May 9, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69ff5f5ddfcc819092563419f9e82d60 |
completed | May 9, 2026, 4:22 p.m. |
Created at: April 27, 2026, 7:12 a.m.