Triple
T75141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Hammann (DD-412) |
E1502
|
entity |
| Predicate | service |
P4690
|
FINISHED |
| Object | Pacific Ocean operations |
—
|
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: Pacific Ocean operations | Statement: [USS Hammann (DD-412), service, Pacific Ocean operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: service Context triple: [USS Hammann (DD-412), service, Pacific Ocean operations]
-
A.
serviceNumber
Indicates a unique identifying number assigned to a service, used to reference, track, or distinguish that service from others.
-
B.
support
Indicates that one entity provides assistance, endorsement, or backing to another entity or its actions.
-
C.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
D.
serviceBranch
Indicates the military or organizational branch in which an entity serves or is affiliated.
-
E.
site
Indicates that one entity is the physical or virtual location where another entity is situated, occurs, or is based.
- 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_69a24c60d19c8190a1b6c105ca59ef5b |
completed | Feb. 28, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69a25314bd6c81908d1cfd4b83f20049 |
completed | Feb. 28, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69a24eae77ec81909015906f31f2b62e |
completed | Feb. 28, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69a25313f1688190ba0fa8677faaf65b |
completed | Feb. 28, 2026, 2:29 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.