Triple
T5212420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memel |
E117663
|
entity |
| Predicate | presentDayCityLocatedOn |
P31256
|
FINISHED |
| Object | Baltic Sea coast |
—
|
LITERAL 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: Baltic Sea coast | Statement: [Memel, presentDayCityLocatedOn, Baltic Sea coast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentDayCityLocatedOn Context triple: [Memel, presentDayCityLocatedOn, Baltic Sea coast]
-
A.
cityLocatedIn
Indicates that a city is geographically situated within a specified larger administrative or territorial region.
-
B.
presentDayLocationCorrespondsTo
chosen
Indicates that the current, real-world location of an entity matches or aligns with a specified reference location.
-
C.
currentCityName
Indicates the name of the city where the entity is currently located.
-
D.
presentDayMunicipality
Indicates that one entity is the current-day municipality encompassing or corresponding to the area or jurisdiction of another (typically historical) entity.
-
E.
capitalPresentDayLocation
Indicates that the predicate specifies the present-day geographic location of a capital city.
- 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_69bd4464ba3c8190bc16b2ebbe42ddb0 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7a730e6c8190ae6082da41ee592a |
completed | March 20, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_69bd77bb4e8c819094b5ac7cf61512f9 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:47 p.m.