Triple
T26649850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayer Rajah Expressway |
E669019
|
entity |
| Predicate | hasElectronicRoadPricing |
P97049
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ayer Rajah Expressway, hasElectronicRoadPricing, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElectronicRoadPricing Context triple: [Ayer Rajah Expressway, hasElectronicRoadPricing, yes]
-
A.
supportsElectronicTollCollection
chosen
Indicates that an entity is capable of handling or is compatible with electronic toll collection systems for automated toll payment.
-
B.
electronicVignetteIntroduced
Indicates that an electronic vignette (a digital road-use or toll permit) has been put into effect or made available for use.
-
C.
hasTollBoothsAt
Indicates that toll booths are present at or associated with a particular location or segment of infrastructure.
-
D.
hasToll
Indicates that the use, access, or passage associated with something requires payment of a toll or fee.
-
E.
hasTollConcession
Indicates that an entity has been granted the right or authorization to collect tolls for the use of a specific infrastructure or service.
- 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_69ee9d00eb5481908d6c6d0ada2f0c9a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6383625cc8190aa223d8ef655743c |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 2:32 a.m.