Triple
T34785762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borough of Stevenage |
E1002799
|
entity |
| Predicate | hasPrimaryCouncil |
P13025
|
FINISHED |
| Object | Stevenage Borough Council |
E305751
|
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: Stevenage Borough Council | Statement: [Borough of Stevenage, hasPrimaryCouncil, Stevenage Borough Council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryCouncil Context triple: [Borough of Stevenage, hasPrimaryCouncil, Stevenage Borough Council]
-
A.
hasCouncilDistrict
Indicates that an entity is located within or represented by a specific council district.
-
B.
hasCityCouncil
chosen
Indicates that an entity is governed or administered by a specific city council.
-
C.
hasCouncilStructure
Indicates that an entity is organized or governed according to a specific council-based structure or system.
-
D.
hasCouncillors
Indicates that an entity is associated with one or more councillors who serve or represent it in an official capacity.
-
E.
hasCountyCouncil
Indicates that an entity is administratively governed or overseen by a specific county council.
- F. None of above.
Provenance (4 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_69f76db47d408190a24fc7164439ea2d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a031e24299c81908dcbbf1b88f43dfd |
completed | May 12, 2026, 12:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a376fa2293c8190b04aca526341a45d |
completed | June 21, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_6a031ce232a48190b62bca3e94162f2f |
completed | May 12, 2026, 12:28 p.m. |
Created at: May 3, 2026, 3:59 p.m.