Triple
T4706165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borough of Crewe and Nantwich |
E104392
|
entity |
| Predicate | hadBoroughStatus |
P58649
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Borough of Crewe and Nantwich, hadBoroughStatus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadBoroughStatus Context triple: [Borough of Crewe and Nantwich, hadBoroughStatus, true]
-
A.
hadBoroughStatusFrom
Indicates that an entity held the legal or administrative status of a borough starting from a specified point in time.
-
B.
hasBorough
Indicates that one entity is located within, belongs to, or is administratively part of a specific borough.
-
C.
hasBoroughCode
Indicates that an entity is associated with a specific borough identified by a particular code.
-
D.
hasBoroughEndpoint
Indicates that something has an endpoint located within a specific borough.
-
E.
hasTownStatus
Indicates that an entity possesses the legal or administrative status of being recognized as a town.
- F. None of above. chosen
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_69bd43eac3c08190af7e4020c6c3704c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650ad0f88190844bfcb46b3071c2 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd621ba7448190a53ab1e2897acf71 |
completed | March 20, 2026, 3:04 p.m. |
| PDg | Predicate description generation | batch_69bd6508e218819086a36236cfa4a249 |
completed | March 20, 2026, 3:17 p.m. |
Created at: March 20, 2026, 1:17 p.m.