Triple
T37371257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilna |
E927848
|
entity |
| Predicate | referentLocatedOnRiver |
P73621
|
FINISHED |
| Object | Neris River |
—
|
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: Neris River | Statement: [Wilna, referentLocatedOnRiver, Neris River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referentLocatedOnRiver Context triple: [Wilna, referentLocatedOnRiver, Neris River]
-
A.
locatedOnBankOfRiver
Indicates that one entity is situated along or directly adjacent to the bank of a specified river.
-
B.
administrativeCenterOnRiver
Indicates that an administrative center (such as a capital or main governing city) is located on the banks of a specified river.
-
C.
locatedInRiverArea
chosen
Indicates that one entity is situated within the geographic area occupied by, adjacent to, or directly associated with a particular river.
-
D.
tookPlaceOnRiver
Indicates that an event or action occurred on or along a specific river.
-
E.
linkedToRiver
Indicates a relationship where something is physically or functionally connected to, associated with, or dependent on a river.
- 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_69f76eb820248190a5c395ca50ad002a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fed6da0390819096b88ef4714b144e |
completed | May 9, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69fed53517d081909966f31707625f1a |
completed | May 9, 2026, 6:33 a.m. |
Created at: May 3, 2026, 4:16 p.m.