Triple
T32445127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BKN |
E829121
|
entity |
| Predicate | informationSystemUsage |
P159713
|
FINISHED |
| Object | used in online railway enquiry systems |
—
|
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: used in online railway enquiry systems | Statement: [BKN, informationSystemUsage, used in online railway enquiry systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: informationSystemUsage Context triple: [BKN, informationSystemUsage, used in online railway enquiry systems]
-
A.
usedByInformationSystems
chosen
Indicates that something (such as a resource, method, or component) is utilized or operated by information systems.
-
B.
technologyUse
Indicates the use or application of a particular technology by an entity to perform an action or achieve a purpose.
-
C.
platformUsage
Indicates how an entity uses, engages with, or relies on a particular platform for its activities or services.
-
D.
technologyUsedFor
Indicates that a particular technology is employed or applied to accomplish, support, or enable a specific purpose, task, or function.
-
E.
usageType
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
- 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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2e5a0ec819098203f775adb5d03 |
completed | May 3, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:55 a.m.