Triple
T19107110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nevsky Express |
E467683
|
entity |
| Predicate | securityMeasuresAfter2009 |
P7757
|
FINISHED |
| Object | increased track 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: increased track security | Statement: [Nevsky Express, securityMeasuresAfter2009, increased track security]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityMeasuresAfter2009 Context triple: [Nevsky Express, securityMeasuresAfter2009, increased track security]
-
A.
securityChangesAfter
chosen
Indicates that the security status or configuration of one entity is modified as a consequence of a prior event or change in another entity.
-
B.
securityMechanisms
Indicates the protective methods, controls, or procedures implemented to safeguard entities from threats, vulnerabilities, or unauthorized actions.
-
C.
safeguardingMeasuresInclude
Indicates that certain specific protective or security measures are contained within, or form part of, a broader set of safeguarding measures.
-
D.
securityArrangements
Indicates the existence, nature, or details of protective measures or safeguards established between or around entities.
-
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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e391245c8190b1393577b61c4f76 |
completed | April 20, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e4b9ac41848190afd0f33b42cebe99 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:04 p.m.