Triple
T31639325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maju Expressway Sdn Bhd |
E807400
|
entity |
| Predicate | alternativeNameOfAssetManaged |
P179525
|
FINISHED |
| Object | MEX |
—
|
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: MEX | Statement: [Maju Expressway Sdn Bhd, alternativeNameOfAssetManaged, MEX]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternativeNameOfAssetManaged Context triple: [Maju Expressway Sdn Bhd, alternativeNameOfAssetManaged, MEX]
-
A.
mainAssetManaged
Indicates that one entity is responsible for managing another entity that serves as the primary or main asset.
-
B.
affectedAsset
Indicates that an entity has an impact on, or causes a change to, a particular asset.
-
C.
operatedAsset
Indicates that one entity is responsible for operating, managing, or running a particular asset.
-
D.
assetTypeMaintained
Indicates that a particular type or category of asset is kept in proper working condition through maintenance activities.
-
E.
typeOfHeritageAssetManaged
Indicates the specific category or kind of heritage asset that an entity is responsible for managing.
- 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_69f348d892948190915f8facacb9568c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f722c1bc648190a79bfdc722dcaaa4 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: April 30, 2026, 10:48 p.m.