Triple
T33111402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German High Seas Fleet |
E847340
|
entity |
| Predicate | locationOfMainOperations |
P32483
|
FINISHED |
| Object | Heligoland Bight |
E304539
|
NE 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: Heligoland Bight | Statement: [German High Seas Fleet, locationOfMainOperations, Heligoland Bight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfMainOperations Context triple: [German High Seas Fleet, locationOfMainOperations, Heligoland Bight]
-
A.
hasBaseOfOperations
chosen
Indicates that an entity uses a particular location as its primary place of operation or activity.
-
B.
hasPrimaryProductionLocation
Indicates that an entity’s main or principal place where it is produced or manufactured is a specified location.
-
C.
headquartersLocation
Indicates the place where an organization’s main administrative center or principal office is located.
-
D.
operationLocation
Indicates the place or site where an operation, activity, or process is carried out.
-
E.
tieneSedePrincipal
Indicates that an entity has its main headquarters or principal office located in a specified place.
- F. None of above.
Provenance (4 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0358c946f08190a8fb41c643074475 |
completed | May 12, 2026, 4:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a35161010f481909de0ac9e70c56782 |
completed | June 19, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_6a03586e5bb08190a71e075fde7cd679 |
completed | May 12, 2026, 4:42 p.m. |
Created at: May 1, 2026, 1:27 a.m.