Triple
T21259477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | thalweg principle |
E523959
|
entity |
| Predicate | definesLocationOf |
P127915
|
FINISHED |
| Object | international boundaries along rivers |
—
|
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: international boundaries along rivers | Statement: [thalweg principle, definesLocationOf, international boundaries along rivers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesLocationOf Context triple: [thalweg principle, definesLocationOf, international boundaries along rivers]
-
A.
definesLocation
chosen
Indicates that one entity specifies or establishes the spatial or geographic position of another entity.
-
B.
marksLocationOf
Indicates that one entity serves as a marker, sign, or indicator specifying the location of another entity.
-
C.
introducedFromLocation
Indicates that something or someone was brought, initiated, or first made present starting from a specified location.
-
D.
subjectLocation
Indicates that one entity is located at, in, or near the place or position specified by another entity.
-
E.
posedAtLocation
Indicates that an entity is positioned or arranged in a deliberate pose at a specific location.
- 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_69e0b5156d7881909bd4f83676590715 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735e53df88190bd6024793a0ada08 |
completed | April 21, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:59 p.m.