Triple
T4251442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crumlin Road |
E95860
|
entity |
| Predicate | policingHistory |
P9816
|
FINISHED |
| Object | heavily policed during the Troubles |
—
|
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: heavily policed during the Troubles | Statement: [Crumlin Road, policingHistory, heavily policed during the Troubles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policingHistory Context triple: [Crumlin Road, policingHistory, heavily policed during the Troubles]
-
A.
administrativeHistory
Indicates the sequence of past administrative changes, statuses, or governing arrangements that have affected an entity over time.
-
B.
legalHistory
Indicates that there exists a record of past legal actions, cases, or statuses associated with an entity.
-
C.
hasLocalGovernmentHistory
Indicates that an entity has a documented history or record of its local governmental structure, activities, or developments.
-
D.
historicalPractice
chosen
Indicates that an action, behavior, or relationship occurred as a customary or established practice during a past historical period.
-
E.
hasHistoricalPolity
Indicates a relationship where an entity is associated with a political unit or state that existed in the past.
- 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_69b3453f759881909b91f01a1e82c036 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34ea059108190aa00f0f20673e0ac |
completed | March 12, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69b347f73e008190a908a48ef389945a |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:06 p.m.