Triple
T31586411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District 2 |
E805966
|
entity |
| Predicate | postalSystemOperator |
P14605
|
FINISHED |
| Object | Singapore Post |
—
|
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: Singapore Post | Statement: [District 2, postalSystemOperator, Singapore Post]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postalSystemOperator Context triple: [District 2, postalSystemOperator, Singapore Post]
-
A.
governingPostalOperator
Indicates that one postal operator has official authority or regulatory control over the operations of another postal service or postal area.
-
B.
postalService
chosen
Indicates a relationship where one entity provides or manages the delivery and handling of mail and packages for another entity.
-
C.
postalServiceDesignation
Indicates the official classification or label assigned to an entity by a postal service for mail handling, routing, or addressing purposes.
-
D.
operatedPostalServiceBrand
Indicates that an entity managed and ran the postal service operations under a specific postal service brand.
-
E.
postalIntegration
Indicates a relationship where one system or entity is connected to and can exchange or synchronize data with a postal or mail-handling system.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a80d41888190aab4fb9229f7fb7d |
completed | May 3, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:26 p.m.