Triple
T1464381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canal Street (Manchester) |
E31585
|
entity |
| Predicate | hasSafetyMeasures |
P22957
|
FINISHED |
| Object | visible security presence on busy nights |
—
|
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: visible security presence on busy nights | Statement: [Canal Street (Manchester), hasSafetyMeasures, visible security presence on busy nights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSafetyMeasures Context triple: [Canal Street (Manchester), hasSafetyMeasures, visible security presence on busy nights]
-
A.
hasSafetyRegulationCompliance
Indicates that an entity adheres to, satisfies, or is in conformity with specified safety regulations or standards.
-
B.
safetyRequirement
Indicates that one entity specifies or imposes conditions, standards, or measures necessary to ensure the safety of another entity or activity.
-
C.
securityArrangementsBy
Indicates that one entity is responsible for providing, organizing, or overseeing security arrangements for another entity or situation.
-
D.
hasSecurityStandard
Indicates that an entity complies with, follows, or is governed by a specified security standard or framework.
-
E.
hasSecurityPresence
chosen
Indicates that some form of security personnel, system, or measures are present at or associated with an entity or location.
- 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c5ba2d5c81909ee85713de961fcb |
completed | March 1, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69a4c48121e48190946c23c583e5fb64 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.