Triple
T24909991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merkys |
E623819
|
entity |
| Predicate | isPrincipalTributaryOf |
P151394
|
FINISHED |
| Object | Neman |
—
|
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: Neman | Statement: [Merkys, isPrincipalTributaryOf, Neman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrincipalTributaryOf Context triple: [Merkys, isPrincipalTributaryOf, Neman]
-
A.
isHeadwaterTributaryOf
Indicates that one watercourse is a source or upstream tributary that feeds into another watercourse.
-
B.
isNaturalTributaryOf
chosen
Indicates that one watercourse flows naturally into another, contributing its water as a tributary without artificial diversion.
-
C.
hasTributaryRelationsWith
Indicates that one entity maintains a tributary relationship with another, typically involving regular payments or offerings in exchange for protection, favor, or acknowledgment of superiority.
-
D.
hasTributaryRelation
Indicates a relationship where one entity serves as a tributary, paying regular tribute or acknowledging subordination to another entity.
-
E.
containsTributariesOf
Indicates that one water body or drainage system includes within it the tributary streams or rivers of another.
- 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 18, 2026, 5:27 a.m.