Triple
T32929706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rapid Rail |
E842366
|
entity |
| Predicate | operatesServiceFrequency |
P55256
|
FINISHED |
| Object | high-frequency urban rail services |
—
|
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 urban rail services | Statement: [Rapid Rail, operatesServiceFrequency, high-frequency urban rail services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesServiceFrequency Context triple: [Rapid Rail, operatesServiceFrequency, high-frequency urban rail services]
-
A.
serviceFrequencyContext
Indicates the contextual conditions or circumstances under which a service’s frequency is defined, applied, or interpreted.
-
B.
serviceFrequencyType
chosen
Indicates how often a service occurs or is scheduled within a given time period.
-
C.
operatesService
Indicates that an agent runs, manages, or provides a particular service.
-
D.
operatesServiceTo
Indicates that one entity runs or provides a transportation or service route to another entity or location.
-
E.
offPeakServiceFrequency_minutes
Indicates the number of minutes between successive services during off-peak periods.
- 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0042524d8c8190884a10fce669ae95 |
completed | May 10, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_6a0041e89bd881909e32764699bcb89b |
completed | May 10, 2026, 8:29 a.m. |
Created at: May 1, 2026, 1:20 a.m.