Triple
T29973991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Express Rail Link to Kuala Lumpur |
E761393
|
entity |
| Predicate | locatedInAirportArea |
P202370
|
FINISHED |
| Object | Sepang |
—
|
NE NERFINISHED |
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: Sepang | Statement: [Express Rail Link to Kuala Lumpur, locatedInAirportArea, Sepang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInAirportArea Context triple: [Express Rail Link to Kuala Lumpur, locatedInAirportArea, Sepang]
-
A.
isLocatedAtAirportType
Indicates that one entity is situated at, or associated with, an airport of a specified type (e.g., international, regional, military).
-
B.
basedInAirport
Indicates that an entity has its primary location, operations, or headquarters situated at a specific airport.
-
C.
locatedAtAirportCode
Indicates that an entity is situated at, associated with, or occurs at the airport identified by a specific airport code.
-
D.
isLocatedAtAirportServingCity
Indicates that something is situated at an airport that provides service to a particular city.
-
E.
partOfAirportLocatedIn
Indicates that a specific part or component of an airport is geographically or administratively located within a particular area or region.
- 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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a00776c4ebc8190899005fda34234d5 |
completed | May 10, 2026, 12:17 p.m. |
| PD | Predicate disambiguation | batch_6a0076f8a4c4819093ed577e67aa38f9 |
completed | May 10, 2026, 12:15 p.m. |
| PDg | Predicate description generation | batch_6a00776b69908190a431a48cc5e7dba9 |
completed | May 10, 2026, 12:17 p.m. |
Created at: April 29, 2026, 6:33 p.m.