Triple
T4096348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birmingham municipal code |
E87829
|
entity |
| Predicate | modifiedThrough |
P8855
|
FINISHED |
| Object | municipal ordinances adopted by Birmingham City Council |
—
|
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: municipal ordinances adopted by Birmingham City Council | Statement: [Birmingham municipal code, modifiedThrough, municipal ordinances adopted by Birmingham City Council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modifiedThrough Context triple: [Birmingham municipal code, modifiedThrough, municipal ordinances adopted by Birmingham City Council]
-
A.
isUpdatedThrough
chosen
Indicates that one entity’s state or content is modified or brought up to date as a result of a process, action, or interaction involving another entity.
-
B.
laterModification
Indicates that one entity is a modification or revision that occurs after another in time.
-
C.
replacedDuring
Indicates that one entity took the place of another entity during a specified time period or interval.
-
D.
mayBeModifiedBy
Indicates that an entity has the potential to be altered, changed, or updated by another entity or process.
-
E.
modification
Indicates a change made to an existing entity, altering its properties, structure, or state from a prior version.
- 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_69aed94564cc8190a9c1457daedb6e7f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefcdef11081908c626a89f2c0e121 |
completed | March 9, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69aef90b2ef08190ae84febfd69dd48b |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:40 p.m.