Triple
T22108280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kilmore, Sleat |
E546345
|
entity |
| Predicate | hasNearbySettlement |
P4647
|
FINISHED |
| Object | Ardvasar |
E1499938
|
NE 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: Ardvasar | Statement: [Kilmore, Sleat, hasNearbySettlement, Ardvasar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ardvasar Context triple: [Kilmore, Sleat, hasNearbySettlement, Ardvasar]
-
A.
Ardvasar
chosen
Ardvasar is a small coastal village on the Isle of Skye in Scotland, known as a ferry port for crossings to the mainland.
-
B.
Argavand
Argavand is a settlement in Armenia situated along the Hrazdan River.
-
C.
Belpahar
Belpahar is a small industrial town in the Jharsuguda district of Odisha, India, known for its coal mining and related industries.
-
D.
Durdhara
Durdhara is traditionally regarded as the wife of the Mauryan emperor Chandragupta Maurya and the mother of his successor, Bindusara, in ancient Indian history.
-
E.
Khansar
Khansar is a historic city in central Iran known for its traditional architecture, cool climate, and production of honey and dairy products.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69e11e378dc08190896d6a51597afd5a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1291adc74819092c7753bb6f3768d |
completed | April 28, 2026, 9:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0a87ac12e881909ba2c0de6f3b26f5 |
completed | May 18, 2026, 3:29 a.m. |
Created at: April 16, 2026, 8:30 p.m.