Triple
T6715651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ballymun |
E153259
|
entity |
| Predicate | hasPlanningChallenge |
P72002
|
FINISHED |
| Object | social deprivation |
—
|
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: social deprivation | Statement: [Ballymun, hasPlanningChallenge, social deprivation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlanningChallenge Context triple: [Ballymun, hasPlanningChallenge, social deprivation]
-
A.
hasPlanningIssue
chosen
Indicates that an entity is associated with a problem, concern, or complication related to planning or plan formulation.
-
B.
hasPlanningGoal
Indicates that an entity is associated with, or directed toward achieving, a specific planning objective or target state.
-
C.
hasPlanningConcept
Indicates that an entity is associated with, defined by, or governed by a particular planning-related concept or framework.
-
D.
hasChallenge
Indicates that an entity faces, experiences, or is confronted with a particular difficulty, obstacle, or problem.
-
E.
hasPlanningStatus
Indicates that an entity is associated with a particular stage, condition, or outcome in a planning or approval process.
- 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_69c68809b4608190a2509ddb5ab87f05 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d1246b748190aed94e8ab8625f7e |
completed | March 27, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69c6d08c5d348190a29dee668c398e70 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:07 p.m.