Triple
T31764713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | List auf Sylt |
E810775
|
entity |
| Predicate | locatedAtNorthernmostPointOf |
P15231
|
FINISHED |
| Object | Germany |
E1728
|
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: Germany | Statement: [List auf Sylt, locatedAtNorthernmostPointOf, Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedAtNorthernmostPointOf Context triple: [List auf Sylt, locatedAtNorthernmostPointOf, Germany]
-
A.
northernmostPoint
Indicates the location that lies furthest to the north within the spatial extent of a given entity.
-
B.
locatedInNorthernmostCityOfCountry
Indicates that an entity is situated within the city that lies furthest north in a given country.
-
C.
isNorthernmost
Indicates that one entity is located farther north than all other comparable entities in a given set or region.
-
D.
isNorthernmostRegionOf
Indicates that one region is the geographically furthest north among all regions within a specified larger area or entity.
-
E.
locatedAtNorthernEndOf
chosen
Indicates that one entity is situated at or near the northernmost part or extremity of another entity.
- 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_69f348e463e08190b902d4819195e1f0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a01bcd39760819081807a02eb1939d1 |
completed | May 11, 2026, 11:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2d9d37a9d48190942dee4b7ade404a |
completed | June 13, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_6a01bc3f1c74819087580e3134affc60 |
completed | May 11, 2026, 11:23 a.m. |
Created at: April 30, 2026, 11:32 p.m.