Triple
T14348554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karak Castle |
E355791
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Karak |
E355791
|
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: Karak | Statement: [Karak Castle, locatedIn, Karak]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Karak Context triple: [Karak Castle, locatedIn, Karak]
-
A.
Karak
Karak is a red-tailed black cockatoo known for serving as the official mascot of the 2006 Commonwealth Games in Melbourne, Australia.
-
B.
Karak
Karak is a town in Pakistan’s Khyber Pakhtunkhwa province known as the headquarters of Karak District and for its surrounding oil and gas reserves.
-
C.
Karak
chosen
Karak is a historic Jordanian city best known for its imposing Crusader-era castle overlooking the surrounding highlands.
-
D.
Karad
Karad is a town in the Satara district of Maharashtra, India, known for its location at the confluence of the Krishna and Koyna rivers and its regional commercial and educational significance.
-
E.
Karam
Karam is a given name commonly used in South Asian and Middle Eastern cultures, often associated with meanings of generosity and nobility.
- 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_69d82790a7e08190877e2d349b2e8d8e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8e8d081c8190ac805726a3e98f4c |
completed | April 14, 2026, 6:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd4c4145c081909832e2334a064fb0 |
completed | May 8, 2026, 2:36 a.m. |
Created at: April 10, 2026, 1:14 a.m.