Triple
T10103529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skudai |
E216259
|
entity |
| Predicate | distanceToJohorBahruCityCentre |
P92441
|
FINISHED |
| Object | approximately 15 kilometres |
—
|
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: approximately 15 kilometres | Statement: [Skudai, distanceToJohorBahruCityCentre, approximately 15 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToJohorBahruCityCentre Context triple: [Skudai, distanceToJohorBahruCityCentre, approximately 15 kilometres]
-
A.
distanceFromKualaLumpur
Indicates the spatial distance between a given location or entity and Kuala Lumpur.
-
B.
distanceFromGeorgeTown
Indicates the measured spatial distance between a given location and George Town.
-
C.
distanceFromKotaBharu
Indicates the spatial distance between an entity’s location and the city of Kota Bharu.
-
D.
nearCityOnMalaysianSide
Indicates that one entity is located close to a particular city that lies on the Malaysian side of a border or region.
-
E.
distanceFromPattayaCityCentre
Indicates the measured distance between a given location and the central area of Pattaya City.
- 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_69ca83d039f08190b9d10363221c69fb |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd09af07c819099774af46ebf62d7 |
completed | April 2, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9b853c8190a2af993ce9b21309 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd5150ae98819086c4f822114b4e2c |
completed | April 1, 2026, 5:09 p.m. |
Created at: March 30, 2026, 9:03 p.m.