Triple
T22558174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stoliv |
E557741
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Perast |
—
|
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: Perast | Statement: [Stoliv, locatedNear, Perast]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Perast Context triple: [Stoliv, locatedNear, Perast]
-
A.
Perast
chosen
Perast is a historic coastal town in Montenegro renowned for its well-preserved Baroque architecture and picturesque setting on the Bay of Kotor.
-
B.
Parastui
Parastui is the surname of Parviz Parastui, a prominent Iranian actor known for his roles in drama and comedy films.
-
C.
Pasca
Pasca is a town in Colombia’s Cundinamarca Department, known as the discovery site of the famous pre-Columbian Muisca golden raft artifact.
-
D.
Prahasta
Prahasta is a powerful rakshasa commander in the Hindu epic Ramayana, serving as one of Ravana’s chief generals in the war against Rama.
-
E.
Perar
Perar is an alternative name for the Bharathapuzha River, one of the major rivers flowing through the Indian state of Kerala.
- 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_69e11e59db848190b4272ecd2b690ffd |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f7b06e08190b3ca82a783965942 |
completed | April 29, 2026, 1:31 a.m. |
Created at: April 16, 2026, 8:52 p.m.