Triple
T32912938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Link Expressway |
E841930
|
entity |
| Predicate | openedPurpose |
P79
|
FINISHED |
| Object | to reduce traffic congestion at the Johor–Singapore Causeway |
—
|
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: to reduce traffic congestion at the Johor–Singapore Causeway | Statement: [Second Link Expressway, openedPurpose, to reduce traffic congestion at the Johor–Singapore Causeway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedPurpose Context triple: [Second Link Expressway, openedPurpose, to reduce traffic congestion at the Johor–Singapore Causeway]
-
A.
entryPurpose
Indicates the reason or intended use for which an entity is being entered, accessed, or recorded in a given context.
-
B.
rangePurpose
Indicates the intended function or use for which a given range or interval is defined.
-
C.
accessPurpose
Indicates that one entity uses or accesses another entity specifically for a defined purpose or intended use.
-
D.
purpose
chosen
Indicates that one entity exists, is done, or is used in order to achieve, support, or serve the goal, function, or intended outcome of another entity.
-
E.
operationalPurpose
Indicates the function, role, or intended use that an entity is designed or configured to perform in an operational context.
- 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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 1, 2026, 1:19 a.m.