Triple
T22891345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Havelock Square |
E568046
|
entity |
| Predicate | streetAddressExample |
P606
|
FINISHED |
| Object | 3 Havelock Square, 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: 3 Havelock Square, Singapore | Statement: [Havelock Square, streetAddressExample, 3 Havelock Square, Singapore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetAddressExample Context triple: [Havelock Square, streetAddressExample, 3 Havelock Square, Singapore]
-
A.
streetAddress
chosen
Indicates the specific location of an entity in terms of its numbered building and street name within a postal address.
-
B.
address
Indicates that one entity directs spoken or written communication specifically to another entity.
-
C.
locationAddressed
Indicates that a communication, message, or action is specifically directed to or intended for a particular location or address.
-
D.
addressExamplePrefix
Indicates that an address example is introduced or categorized by a specific prefix string used to distinguish or group it.
-
E.
streetAddressContains
Indicates that one street address string includes another address-related string as a substring or component.
- 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_69e2458c23ec81908fa2570692c6614f |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f17fc59e108190a22f90c2439830fb |
completed | April 29, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69ef3b6b2e2481908258156937b5a745 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:40 p.m.