Triple
T26382635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Loch |
E663176
|
entity |
| Predicate | USNBaseEstablished |
P32492
|
FINISHED |
| Object | 1961 |
—
|
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: 1961 | Statement: [Holy Loch, USNBaseEstablished, 1961]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: USNBaseEstablished Context triple: [Holy Loch, USNBaseEstablished, 1961]
-
A.
associatedWithNavalBase
Indicates a relationship in which an entity is connected or linked to a naval base, such as by location, operation, support, or administration.
-
B.
USNDesignation
Indicates the formal designation assigned by the United States Navy to identify and classify a ship, aircraft, or other naval asset.
-
C.
establishedAsNavalBase
chosen
Indicates that a location was formally designated and put into use as a naval base.
-
D.
isNavalBase
Indicates that a location functions as a naval base, serving as an operational facility or station for naval forces.
-
E.
USSignatory
Indicates that an entity is a party that has formally signed or agreed to a treaty, agreement, or document on behalf of or under the jurisdiction of the United States.
- 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_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 11:19 p.m.