Triple
T5560852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keystone Service |
E145760
|
entity |
| Predicate | frequencyCharacteristic |
P27106
|
FINISHED |
| Object | high-frequency regional service |
—
|
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-frequency regional service | Statement: [Keystone Service, frequencyCharacteristic, high-frequency regional service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequencyCharacteristic Context triple: [Keystone Service, frequencyCharacteristic, high-frequency regional service]
-
A.
frequency
Indicates how often an event, action, or relationship occurs within a given period or context.
-
B.
frequencyDependsOn
Indicates that the frequency of one event, action, or state is determined or influenced by another factor or condition.
-
C.
frequencyRegion
chosen
Indicates that something is associated with, occurs within, or is characterized by a particular range or band of frequencies.
-
D.
frequencyClass
Indicates how often an event, action, or relation occurs, typically by assigning it to a predefined frequency category or class.
-
E.
frequencyChange
Indicates a change in how often an event, action, or state occurs over time.
- 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_69c008fcaf788190bafa02a1917ee73b |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0201857848190a5443b51bcdb63fa |
completed | March 22, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69c01b10bbf8819098655839c03b7832 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.