Triple
T25624436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puncak area |
E642389
|
entity |
| Predicate | transportIssue |
P72800
|
FINISHED |
| Object | one-way traffic management on busy days |
—
|
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: one-way traffic management on busy days | Statement: [Puncak area, transportIssue, one-way traffic management on busy days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportIssue Context triple: [Puncak area, transportIssue, one-way traffic management on busy days]
-
A.
hasTransportIssue
chosen
Indicates that an entity is experiencing a problem, disruption, or malfunction related to transportation or a transport service.
-
B.
fareProblem
Indicates that there is an issue, dispute, or irregularity related to the fare charged or paid for a trip or service.
-
C.
carriageIssues
Indicates that there are problems, malfunctions, or irregularities affecting the operation or condition of a carriage.
-
D.
transportationFunction
Indicates that one entity serves to move or carry another entity from one place to another.
-
E.
causedTransportDisruption
Indicates that one entity was the cause of a disruption or interruption to the normal operation of a transport system or service.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 21, 2026, 5:07 p.m.