Triple
T36149543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woodlands East |
E1045546
|
entity |
| Predicate | isNorthernSubzoneOf |
P184959
|
FINISHED |
| Object | Woodlands Planning Area |
—
|
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: Woodlands Planning Area | Statement: [Woodlands East, isNorthernSubzoneOf, Woodlands Planning Area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNorthernSubzoneOf Context triple: [Woodlands East, isNorthernSubzoneOf, Woodlands Planning Area]
-
A.
isNorthernmostRegionOf
Indicates that one region is the geographically furthest north among all regions within a specified larger area or entity.
-
B.
northernRegionAdjacentTo
Indicates that one region is directly next to another and lies to its north.
-
C.
northTerminusRegion
Indicates that a specified region serves as the northern endpoint or terminus of a linear feature, route, or entity.
-
D.
locatedInNorthernOrSouthernPartOfRegion
Indicates that an entity is situated in either the northern or southern part of a specified region.
-
E.
isNorthernCommunityOf
Indicates that one community is geographically located to the north of another community.
- 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_69f76e37ace88190a906b107d388f5d1 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b69a74a08190b31b1201278a2c57 |
completed | May 3, 2026, 8:56 p.m. |
Created at: May 3, 2026, 4:08 p.m.