Triple
T32774541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estonia |
E838158
|
entity |
| Predicate | hasNavalBaseOn |
P32766
|
FINISHED |
| Object | Gulf of Finland |
—
|
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: Gulf of Finland | Statement: [Estonia, hasNavalBaseOn, Gulf of Finland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNavalBaseOn Context triple: [Estonia, hasNavalBaseOn, Gulf of Finland]
-
A.
isNavalBase
Indicates that a location functions as a naval base, serving as an operational facility or station for naval forces.
-
B.
hasNavalFacility
chosen
Indicates that one entity possesses, hosts, or contains a naval facility (such as a naval base, port, or installation) associated with it.
-
C.
navalBaseLocation
Indicates the geographic location where a naval base is situated or established.
-
D.
associatedWithNavalBase
Indicates a relationship in which an entity is connected or linked to a naval base, such as by location, operation, support, or administration.
-
E.
navalCountry
Indicates that a country possesses or operates a navy, signifying its involvement in naval or maritime military activities.
- 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_69f3493a824c8190938489ba69041d08 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fea2d0a4d08190aa06aeb902a02d5a |
completed | May 9, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fea24698348190b9b992a8e7cdbcd0 |
completed | May 9, 2026, 2:56 a.m. |
Created at: May 1, 2026, 1:13 a.m.