Triple
T19320418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bessbrook |
E483207
|
entity |
| Predicate | planningFeatures |
P80690
|
FINISHED |
| Object | workers’ housing |
—
|
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: workers’ housing | Statement: [Bessbrook, planningFeatures, workers’ housing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planningFeatures Context triple: [Bessbrook, planningFeatures, workers’ housing]
-
A.
featuresIn
chosen
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
-
B.
planningSkill
Indicates the degree to which an entity is capable of effectively organizing, sequencing, and coordinating actions or resources to achieve goals.
-
C.
planning
Indicates that an entity is engaged in organizing or devising a future action, event, or course of behavior involving another entity or entities.
-
D.
urbanPlanningFunction
Indicates a functional role or purpose that something serves within the planning, organization, or management of urban spaces and infrastructure.
-
E.
featuresBuilding
Indicates that one entity includes or incorporates a building as a notable component or characteristic.
- 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e60d87a0088190a60201b1f388089e |
completed | April 20, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0ef66881909d489d634eee817a |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:32 p.m.