Triple
T28874419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iskandar Puteri |
E732226
|
entity |
| Predicate | hasPlannedArea |
P60867
|
FINISHED |
| Object | residential zones |
—
|
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: residential zones | Statement: [Iskandar Puteri, hasPlannedArea, residential zones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlannedArea Context triple: [Iskandar Puteri, hasPlannedArea, residential zones]
-
A.
plannedArea
chosen
Indicates that an area is designated or intended for a specific planned use or development.
-
B.
hasPlannedSectors
Indicates that an entity is associated with specific sectors that have been identified or designated in advance for future activity, development, or focus.
-
C.
hasAllotmentArea
Indicates that an entity is associated with a specific area of land that has been formally allotted or assigned to it.
-
D.
hasAreaType
Indicates that an entity is associated with a specific kind or classification of area (e.g., urban, rural, coastal).
-
E.
hasPlannedPart
Indicates that one entity includes another entity as a component or segment within a planned or scheduled whole.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 28, 2026, 7:36 a.m.