Triple
T31223757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS George Washington (SSBN-598) |
E796082
|
entity |
| Predicate | locationOfSail |
P13806
|
FINISHED |
| Object | Groton, Connecticut |
—
|
NE NERFINISHED |
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: Groton, Connecticut | Statement: [USS George Washington (SSBN-598), locationOfSail, Groton, Connecticut]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfSail Context triple: [USS George Washington (SSBN-598), locationOfSail, Groton, Connecticut]
-
A.
sailPlan
Indicates a plan or arrangement for how a vessel will be sailed, including intended route, timing, and sailing configuration.
-
B.
sailingVenue
chosen
Indicates the location or facility where sailing activities or events take place.
-
C.
sailingRoute
Indicates a path or course taken by a vessel when traveling by water from one location to another.
-
D.
sailingStatus
Indicates the current operational state or condition of a vessel in relation to its sailing activity (e.g., underway, docked, anchored, or out of service).
-
E.
sailNumber
Indicates the identifying number assigned to a specific sail or sailing vessel, typically used to distinguish it from others.
- 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_69f224da98f88190ab32f690cce5d303 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a016b2629c48190befb10581560d58f |
completed | May 11, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_6a0167d5a2088190a68dbd2b87f73e80 |
completed | May 11, 2026, 5:23 a.m. |
Created at: April 29, 2026, 9:10 p.m.