Triple
T36149476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Region |
E1045545
|
entity |
| Predicate | directionalLocation |
P30236
|
FINISHED |
| Object | Northern Singapore |
—
|
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: Northern Singapore | Statement: [North Region, directionalLocation, Northern Singapore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionalLocation Context triple: [North Region, directionalLocation, Northern Singapore]
-
A.
directionRelativeTo
Indicates the spatial orientation of one entity in relation to another, such as which way it faces or points relative to a reference entity.
-
B.
directionBy
Indicates that one entity provides directional guidance, orientation, or navigational reference for another entity.
-
C.
directionalDesignation
chosen
Indicates a relationship where one entity is assigned or labeled with a specific directional orientation relative to another entity or reference frame.
-
D.
latitudeDirection
Indicates the cardinal direction (north or south) associated with a given latitude value relative to the equator.
-
E.
directionalRole
Indicates a role or function defined in terms of a direction or orientation relative to another entity or reference frame.
- 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_69f76e37ace88190a906b107d388f5d1 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: May 3, 2026, 4:08 p.m.