Triple
T37966063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cumberland County |
E947145
|
entity |
| Predicate | partlyRecreatedAs |
P87970
|
FINISHED |
| Object | Cumberland (unitary authority) |
—
|
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: Cumberland (unitary authority) | Statement: [Cumberland County, partlyRecreatedAs, Cumberland (unitary authority)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partlyRecreatedAs Context triple: [Cumberland County, partlyRecreatedAs, Cumberland (unitary authority)]
-
A.
partlyRebuilt
Indicates that an entity has been reconstructed or restored to some extent, but not fully.
-
B.
recreated
Indicates that an entity has been created again or restored, typically after being removed, destroyed, or significantly altered.
-
C.
reconstructedAsPartOf
chosen
Indicates that one entity has been rebuilt, restored, or recreated as a component or segment of another, larger whole.
-
D.
restoredInPart
Indicates that something has been brought back to a previous or improved state, but only partially rather than fully.
-
E.
recreatedFor
Indicates that one entity has been created again or reproduced specifically for the benefit, use, or purpose of another entity.
- 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_69f76ef7062c819091bfacb7e83aa1e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc995dc2481908b3bd4217f8101e7 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.