Triple
T22737857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liepāja Lake |
E562322
|
entity |
| Predicate | separatingFeatureFor |
P1175
|
FINISHED |
| Object | city of Liepāja and the Baltic Sea |
—
|
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: city of Liepāja and the Baltic Sea | Statement: [Liepāja Lake, separatingFeatureFor, city of Liepāja and the Baltic Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separatingFeatureFor Context triple: [Liepāja Lake, separatingFeatureFor, city of Liepāja and the Baltic Sea]
-
A.
separationMethod
Indicates the technique or process used to separate one substance, component, or entity from another.
-
B.
typeOfSeparation
Indicates the specific manner or category of separation that exists or occurred between entities.
-
C.
decisiveFeature
Indicates that one feature or characteristic plays a determining role in deciding an outcome or distinguishing between alternatives.
-
D.
providesSeparationFor
Indicates that one entity serves to divide, isolate, or keep another entity apart from something else.
-
E.
separates
chosen
Indicates that one entity divides, parts, or keeps other entities apart from each other.
- 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_69e245513a5c81908d5cb471b4fc429d |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f179707fd081909aed9b2f62b9f842 |
completed | April 29, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69eed2a971c0819088af574e40c9343f |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:22 p.m.