Triple
T30571964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muar District |
E778143
|
entity |
| Predicate | hasRiversideTown |
P26693
|
FINISHED |
| Object | Muar |
—
|
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: Muar | Statement: [Muar District, hasRiversideTown, Muar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiversideTown Context triple: [Muar District, hasRiversideTown, Muar]
-
A.
isRiverside
Indicates that one entity is located beside or along the bank of a river in relation to another entity.
-
B.
hasTownOnRiver
chosen
Indicates that a town is situated on or directly adjacent to a particular river.
-
C.
isRiversideRangeOf
Indicates that something is a range or stretch of land that lies along the side of a river.
-
D.
hasRiverCommunity
Indicates that there is a community located along, dependent on, or closely associated with a particular river.
-
E.
hasMajorTownOnRiver
Indicates that a major town is located on and directly associated with a particular river.
- 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_69f2249f8c148190ae7eb3912cde112a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 29, 2026, 8:22 p.m.