Triple
T26997193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District Courts of Nepal |
E680006
|
entity |
| Predicate | hasOneCourtPer |
P27149
|
FINISHED |
| Object | district of Nepal |
—
|
LITERAL 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: district of Nepal | Statement: [District Courts of Nepal, hasOneCourtPer, district of Nepal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOneCourtPer Context triple: [District Courts of Nepal, hasOneCourtPer, district of Nepal]
-
A.
associatedWithCourt
Indicates a relationship in which an entity is linked or connected to a specific court, such as through jurisdiction, affiliation, or involvement in legal proceedings.
-
B.
hasCourtInEach
chosen
Indicates that an entity possesses or maintains a court in every member of a specified set of locations or jurisdictions.
-
C.
hostCourtOf
Indicates that one entity serves as the venue or location where the court associated with another entity is held or convened.
-
D.
hasCourtroomsFor
Indicates that an entity provides or contains courtrooms designated for use by another entity or purpose.
-
E.
hasTypeOfCourt
Indicates that an entity is associated with or classified by a specific type or category of court.
- F. None of above.
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_69eeeb52908c8190bd246244686aa455 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 27, 2026, 6:55 a.m.