Triple
T36058086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Express Rail Link |
E1043001
|
entity |
| Predicate | travelTimeKLIAEkspres |
P39869
|
FINISHED |
| Object | about 28 minutes between KL Sentral and KLIA |
—
|
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: about 28 minutes between KL Sentral and KLIA | Statement: [Express Rail Link, travelTimeKLIAEkspres, about 28 minutes between KL Sentral and KLIA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelTimeKLIAEkspres Context triple: [Express Rail Link, travelTimeKLIAEkspres, about 28 minutes between KL Sentral and KLIA]
-
A.
travelTimeFromKotaKinabalu
Indicates the amount of time required to travel from Kota Kinabalu to another specified location or entity.
-
B.
distanceFromKualaLumpur
Indicates the spatial distance between a given location or entity and Kuala Lumpur.
-
C.
travelTimeFromJakartaByCar
Indicates the amount of time it takes to travel by car from Jakarta to a specified destination.
-
D.
distanceToAlorSetar_km
Indicates the distance, measured in kilometers, from a given location to Alor Setar.
-
E.
travelTimeToAirport
chosen
Indicates the amount of time required to travel from a given location to an airport.
- 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_69f76e2f09448190b0486d5ecad5e243 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.