Triple
T15762859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hemnes |
E382140
|
entity |
| Predicate | borders |
P224
|
FINISHED |
| Object | Rana |
E381846
|
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: Rana | Statement: [Hemnes, borders, Rana]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rana Context triple: [Hemnes, borders, Rana]
-
A.
Rana
Rana is a large and widespread genus of true frogs that includes many familiar pond and stream-dwelling species found across much of the world.
-
B.
Rana
Rana was the hereditary royal title borne by the ruling dynasty of the former princely state of Porbandar in western India.
-
C.
Rana
chosen
Rana is a large municipality in Nordland county, Norway, known for the town of Mo i Rana and its dramatic fjords, mountains, and caves just south of the Arctic Circle.
-
D.
Rana
Rana is a feminine given name of Arabic origin commonly used across the Middle East and other regions.
-
E.
Rana uenoi
Rana uenoi is a species of true frog in the genus Rana, native to parts of East Asia and typically associated with freshwater habitats.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e050b6c9fc8190a1bcf763c4b04b12 |
completed | April 16, 2026, 3 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff8776c2488190ad27fd79e2ce4e14 |
completed | May 9, 2026, 7:13 p.m. |
Created at: April 10, 2026, 4:47 a.m.