Triple
T26382633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Loch |
E663176
|
entity |
| Predicate | navalUseStart |
P42687
|
FINISHED |
| Object | World War I era |
—
|
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: World War I era | Statement: [Holy Loch, navalUseStart, World War I era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalUseStart Context triple: [Holy Loch, navalUseStart, World War I era]
-
A.
navalOperationsCeased
Indicates that naval activities or missions have been stopped or brought to an end.
-
B.
establishedAsNavalBase
Indicates that a location was formally designated and put into use as a naval base.
-
C.
navalPolicy
Indicates the policies, strategies, or regulatory stance a state or authority adopts regarding the organization, deployment, and use of its naval forces.
-
D.
navalOperationsBy
Indicates that a set of naval operations is conducted, controlled, or carried out by a specified agent or organization.
-
E.
navalEra
chosen
Indicates the historical period or era in which a naval-related event, activity, or condition takes place.
- 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.