Triple
T18381179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Putna River |
E446447
|
entity |
| Predicate | hasNameInLanguage |
P15
|
FINISHED |
| Object | Putna@ro |
—
|
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: Putna@ro | Statement: [Putna River, hasNameInLanguage, Putna@ro]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Putna@ro Context triple: [Putna River, hasNameInLanguage, Putna@ro]
-
A.
Putna
Putna is a village in Suceava County, Romania, best known as a major Romanian Orthodox pilgrimage site centered around the historic Putna Monastery.
-
B.
Putna
chosen
Putna is a river in eastern Romania that flows through the historical region of Moldavia before joining the Siret River.
-
C.
Pustec
Pustec is a small municipality in southeastern Albania, known for its ethnic Macedonian community and its location on the shores of Lake Prespa.
-
D.
Răut
Răut is a river in Moldova that flows through the central part of the country before joining the Dniester.
-
E.
Pașcani
Pașcani is a town in northeastern Romania known as an important local railway junction and administrative center within the historical region of Moldavia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e5179b60f88190adf39e85375bd11b |
completed | April 19, 2026, 5:57 p.m. |
Created at: April 10, 2026, 10:45 a.m.