Triple
T21144718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birmingham District |
E521022
|
entity |
| Predicate | developedRapidlyIn |
P16148
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Birmingham District, developedRapidlyIn, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedRapidlyIn Context triple: [Birmingham District, developedRapidlyIn, late 19th century]
-
A.
developedRapidlyDuring
chosen
Indicates that one entity experienced swift or accelerated development within the time period or context defined by another entity.
-
B.
developedAlong
Indicates that something was created, constructed, or evolved following the course, path, or boundary of something else.
-
C.
developed
Indicates that one entity created, designed, or brought another entity into a more advanced or complete state through effort or work.
-
D.
developedThrough
Indicates that something came into existence, was created, or was brought to its current form by means of a specified process, method, or developmental pathway.
-
E.
developedWithin
Indicates that something was created, produced, or brought into existence inside a specified context, boundary, or time frame.
- 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_69e0b50c6a848190a4e525a77a319b8a |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e723fbb29881909c4036eab46ed440 |
completed | April 21, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:57 p.m.