Triple
T753755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crumlin Road Gaol |
E15506
|
entity |
| Predicate | securityClass |
P406
|
FINISHED |
| Object | high security |
—
|
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: high security | Statement: [Crumlin Road Gaol, securityClass, high security]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityClass Context triple: [Crumlin Road Gaol, securityClass, high security]
-
A.
securityClassification
chosen
Indicates the level or category of security sensitivity or access restriction assigned to an entity.
-
B.
securityType
Indicates the classification or category of security associated with an entity, such as the type of financial instrument, protection mechanism, or access control applied.
-
C.
securityRole
Indicates that an entity holds a specific security-related role, permission level, or access profile within a system or context.
-
D.
securityAspect
Indicates a relationship where something pertains to, represents, or characterizes a particular aspect or dimension of security.
-
E.
securityArrangementsBy
Indicates that one entity is responsible for providing, organizing, or overseeing security arrangements for another entity or situation.
- 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_69a493599a0081908da65f3407af1ef2 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a64ecadc8190a82e25444e7abba6 |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a501c4cc81908de6d63e3d4f60d7 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.