Triple
T21912879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naval Submarine Base New London |
E541108
|
entity |
| Predicate | homeportFor |
P3150
|
FINISHED |
| Object | United States Navy attack submarines |
—
|
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: United States Navy attack submarines | Statement: [Naval Submarine Base New London, homeportFor, United States Navy attack submarines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeportFor Context triple: [Naval Submarine Base New London, homeportFor, United States Navy attack submarines]
-
A.
homeportCity
Indicates the city that serves as the primary home port or base location for a vessel or similar entity.
-
B.
homePort
chosen
Indicates that a vessel or mobile entity is based at, registered to, or primarily operates from a particular port or harbor.
-
C.
laterHomePort
Indicates that one location served as the subsequent or later home port of a vessel or entity after an earlier home port.
-
D.
homeportRegion
Indicates the geographic region where a vessel’s primary homeport is located.
-
E.
homeportDuringWar
Indicates that an entity served as the designated home port or primary base for another entity during a period of war.
- 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_69e0c47c4b9c8190a5586a75f5f36453 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f121db1dc48190af5dc634431d863a |
completed | April 28, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69e6be9ebf4c8190892df1a8e1313f88 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:41 p.m.