Triple
T35152985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trossö |
E1015042
|
entity |
| Predicate | foundedAsNavalTownFor |
P198535
|
FINISHED |
| Object | Swedish Navy |
—
|
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: Swedish Navy | Statement: [Trossö, foundedAsNavalTownFor, Swedish Navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsNavalTownFor Context triple: [Trossö, foundedAsNavalTownFor, Swedish Navy]
-
A.
foundedAsSettlementFor
Indicates that one entity was originally established specifically to serve as a settlement for another entity (such as a group, population, or community).
-
B.
wasFirstMajorSeaportOf
Indicates that one place served as the earliest significant seaport for another place or region.
-
C.
foundedAsPort
Indicates that a settlement, city, or location was originally established specifically to serve as a port or harbor.
-
D.
isMainHarbourOf
Indicates that a harbour serves as the primary or principal port facility for a specified location or region.
-
E.
foundedAsCanalTown
Indicates that a settlement was originally established specifically as a canal town, typically to serve transportation or trade along a canal.
- F. None of above. chosen
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_69f76ddb3a708190b521ba2970b17178 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fef112398081909237c3872345968b |
completed | May 9, 2026, 8:32 a.m. |
| PD | Predicate disambiguation | batch_69feefb14ec08190ab401987d8c84a23 |
completed | May 9, 2026, 8:26 a.m. |
| PDg | Predicate description generation | batch_69fef1112b0c8190a8eb027edb71e4e0 |
completed | May 9, 2026, 8:32 a.m. |
Created at: May 3, 2026, 4:02 p.m.