Triple
T26382636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Loch |
E663176
|
entity |
| Predicate | USNBaseClosed |
P85703
|
FINISHED |
| Object | 1992 |
—
|
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: 1992 | Statement: [Holy Loch, USNBaseClosed, 1992]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: USNBaseClosed Context triple: [Holy Loch, USNBaseClosed, 1992]
-
A.
closedAsUSBase
chosen
Indicates that a location or facility was closed specifically for use as a United States military base.
-
B.
closedAsUSBaseIn
Indicates that a location ceased operations specifically as a U.S. military base in the specified place or jurisdiction.
-
C.
UNCLOSPartInvoked
Indicates that a specific part or provision of the United Nations Convention on the Law of the Sea (UNCLOS) is cited, applied, or relied upon in a legal or regulatory context.
-
D.
decommissionedFromUSN
Indicates that something was formally retired or removed from active service in the United States Navy.
-
E.
firstUnitsClosed
Indicates that the initial set of units in a sequence, batch, or process has been completed or closed.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f61076a94481909251f4042116768a |
completed | May 2, 2026, 2:55 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 11:19 p.m.