Triple
T214552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VRE |
E4789
|
entity |
| Predicate | fareIntegration |
P8545
|
FINISHED |
| Object | partial integration with regional transit passes |
—
|
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: partial integration with regional transit passes | Statement: [VRE, fareIntegration, partial integration with regional transit passes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareIntegration Context triple: [VRE, fareIntegration, partial integration with regional transit passes]
-
A.
fareSystem
Indicates a relationship where a system is used to determine, collect, or manage fares or payments for transportation or similar services.
-
B.
fareControl
Indicates that an entity is responsible for monitoring, enforcing, or managing payment of fares for access to a service or facility.
-
C.
fareDiscount
Indicates that a reduced price is applied to a standard fare for a product or service.
-
D.
hasFareControlIntegrationSince
Indicates that a fare control system has been integrated with another system or entity starting from a specific point in time.
-
E.
featuresCharge
Indicates that one entity includes, offers, or is characterized by a particular charge (such as a fee, cost, or pricing component).
- F. None of above. chosen
Provenance (4 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_69a2575cb1dc8190a01ad332426dc339 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c32ae208190a03d504ef43ea659 |
completed | Feb. 28, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69a25b509400819093a6c1a1bac861e3 |
completed | Feb. 28, 2026, 3:04 a.m. |
| PDg | Predicate description generation | batch_69a25c036b54819090a101c4cbdbcff7 |
completed | Feb. 28, 2026, 3:07 a.m. |
Created at: Feb. 28, 2026, 2:52 a.m.