Triple
T35166086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastside, Birmingham |
E1015406
|
entity |
| Predicate | regenerationBeganIn |
P30447
|
FINISHED |
| Object | early 2000s |
—
|
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: early 2000s | Statement: [Eastside, Birmingham, regenerationBeganIn, early 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regenerationBeganIn Context triple: [Eastside, Birmingham, regenerationBeganIn, early 2000s]
-
A.
regenerationStartedIn
chosen
Indicates that a regeneration process was initiated or began within a specified location, context, or time frame.
-
B.
regenerationOf
Indicates that one entity is the renewed, restored, or regrown version of another entity, typically after damage, loss, or degradation.
-
C.
regenerationContinuedIn
Indicates that an ongoing process of regeneration persists or is maintained within a specified context, location, or time period.
-
D.
regeneratedWhen
Indicates that an entity is brought back, restored, or recreated at a specific time or under specific conditions.
-
E.
regenerationNumber
Indicates the specific iteration or cycle count of a repeated regeneration or renewal event associated with an 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_69f76ddbfde081908bffc91572368289 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78d34109c8190acd2299e5f73fd1a |
completed | May 3, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.