Triple
T34461693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Wyoming (BB-32) |
E884657
|
entity |
| Predicate | homeportDuringCareer |
P178969
|
FINISHED |
| Object | Atlantic Fleet bases |
—
|
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: Atlantic Fleet bases | Statement: [USS Wyoming (BB-32), homeportDuringCareer, Atlantic Fleet bases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeportDuringCareer Context triple: [USS Wyoming (BB-32), homeportDuringCareer, Atlantic Fleet bases]
-
A.
homeportDuringWar
Indicates that an entity served as the designated home port or primary base for another entity during a period of war.
-
B.
homeportCity
Indicates the city that serves as the primary home port or base location for a vessel or similar entity.
-
C.
homeportAsNOAA
Indicates that a vessel’s designated home port is assigned or recognized specifically as a NOAA (National Oceanic and Atmospheric Administration) home port.
-
D.
homeportDuringColdWar
Indicates that one entity served as the designated home port of the other during the Cold War period.
-
E.
homeportRegion
Indicates the geographic region where a vessel’s primary homeport is located.
- 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_69f349c73a94819094dfcf50d00620b8 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f719cc31ec819099bebcf833b14d76 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f719458378819081725f544efb1173 |
completed | May 3, 2026, 9:45 a.m. |
Created at: May 1, 2026, 2 a.m.