Triple
T34716881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Langholm Cricket Club |
E1000800
|
entity |
| Predicate | basedInCouncilArea |
P76027
|
FINISHED |
| Object | Dumfries and Galloway |
—
|
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: Dumfries and Galloway | Statement: [Langholm Cricket Club, basedInCouncilArea, Dumfries and Galloway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedInCouncilArea Context triple: [Langholm Cricket Club, basedInCouncilArea, Dumfries and Galloway]
-
A.
locatedInRegionalCouncil
Indicates that one entity is geographically situated within the jurisdictional area governed by a specific regional council.
-
B.
isCityCouncilArea
Indicates that a given geographic or administrative region functions as a city council jurisdiction or area of authority.
-
C.
containsRegionalCouncil
Indicates that one administrative or geographic entity includes a regional council within its jurisdiction or boundaries.
-
D.
hasCountyCouncil
Indicates that an entity is administratively governed or overseen by a specific county council.
-
E.
associatedWithCouncilArea
chosen
Indicates that an entity has a formal or contextual relationship with a specific council (administrative) area.
- 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_69f76dad3f108190a280fd0a2f4ee89a |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff0d80c0dc81909fbd12285c7a45c0 |
completed | May 9, 2026, 10:33 a.m. |
| PD | Predicate disambiguation | batch_69ff0cd03e78819094895058f925fbfa |
completed | May 9, 2026, 10:30 a.m. |
Created at: May 3, 2026, 3:59 p.m.