Triple
T37416124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyberjaya Utara MRT station |
E929713
|
entity |
| Predicate | servesTechHub |
P423
|
FINISHED |
| Object | Cyberjaya tech hub |
—
|
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: Cyberjaya tech hub | Statement: [Cyberjaya Utara MRT station, servesTechHub, Cyberjaya tech hub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesTechHub Context triple: [Cyberjaya Utara MRT station, servesTechHub, Cyberjaya tech hub]
-
A.
serviceTechnology
Indicates that a particular technology is used to implement, support, or deliver a given service.
-
B.
offersTechnology
Indicates that one entity provides or makes available a technology or technological solution to another entity.
-
C.
hubFor
chosen
Indicates that one entity serves as a central node or focal point through which activities, connections, or resources related to another entity are organized or routed.
-
D.
addsTechnology
Indicates that one entity incorporates or introduces a specific technology into another entity, system, or context.
-
E.
serviceFor
Indicates that one entity provides a service or performs functions on behalf of another entity.
- 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_69f76ebde49481908566cd96b37ccc84 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a006ef900148190ba52daf566882a03 |
completed | May 10, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_6a006c76ae748190bfe466d7d17d321e |
completed | May 10, 2026, 11:31 a.m. |
Created at: May 3, 2026, 4:16 p.m.