Triple
T23937598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Local Government (Dublin) Act 1993 |
E602680
|
entity |
| Predicate | reorganisedEntity |
P1504
|
FINISHED |
| Object | County Dublin |
—
|
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: County Dublin | Statement: [Local Government (Dublin) Act 1993, reorganisedEntity, County Dublin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reorganisedEntity Context triple: [Local Government (Dublin) Act 1993, reorganisedEntity, County Dublin]
-
A.
reorganizedAs
chosen
Indicates that an existing entity has been restructured or reconfigured into a new organizational form or arrangement.
-
B.
reorganizedIn
Indicates that an entity underwent a structural or organizational change within a specified context, time, or framework.
-
C.
reorganized
Indicates that an entity has changed the structure, order, or arrangement of another entity or set of entities from a previous configuration.
-
D.
reorganizedDueTo
Indicates that one entity was reorganized as a consequence of, or in response to, another specified factor, event, or condition.
-
E.
renamedEntity
Indicates that one entity has been given a new name, linking the original entity to its updated or replacement name.
- 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_69e2953cf6e081909b8e25a10a52dddc |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1cfa1336c8190ac307a1b9497ba0b |
completed | April 29, 2026, 9:30 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:05 p.m.