Triple
T36149571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Coast |
E1045548
|
entity |
| Predicate | regionDirection |
P201641
|
FINISHED |
| Object | northern Singapore |
—
|
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: northern Singapore | Statement: [North Coast, regionDirection, northern Singapore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionDirection Context triple: [North Coast, regionDirection, northern Singapore]
-
A.
latitudeDirection
Indicates the cardinal direction (north or south) associated with a given latitude value relative to the equator.
-
B.
directionWithinRegion
Indicates that a specified direction or heading is located entirely inside the boundaries of a given geographic or spatial region.
-
C.
directionBy
Indicates that one entity provides directional guidance, orientation, or navigational reference for another entity.
-
D.
geographicDirectionWithinCountry
Indicates that one place lies in a specified cardinal or intercardinal direction relative to another place within the same country.
-
E.
geographicalDirectionInProvince
Indicates that one place lies in a specified geographical direction within the boundaries of a given province.
- 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_6a000fda03948190881b7275f249768f |
completed | May 10, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_6a000f607f1881908ee750d58da91690 |
completed | May 10, 2026, 4:53 a.m. |
| PDg | Predicate description generation | batch_6a000fd9602481909ffdc409ac9ca4bb |
completed | May 10, 2026, 4:55 a.m. |
Created at: May 3, 2026, 4:08 p.m.