Triple
T30268522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Post Office Bay |
E769720
|
entity |
| Predicate | postalRequirement |
P44631
|
FINISHED |
| Object | no postage required |
—
|
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: no postage required | Statement: [Post Office Bay, postalRequirement, no postage required]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postalRequirement Context triple: [Post Office Bay, postalRequirement, no postage required]
-
A.
postalService
Indicates a relationship where one entity provides or manages the delivery and handling of mail and packages for another entity.
-
B.
stampRequirementFor
chosen
Indicates that one entity specifies or imposes a required stamp (e.g., type, presence, or condition of a stamp) that must be satisfied for another entity.
-
C.
postUSUse
Indicates a relationship where something is used, applied, or occurs after being in the United States or following a U.S.-related phase or context.
-
D.
postalServiceDesignation
Indicates the official classification or label assigned to an entity by a postal service for mail handling, routing, or addressing purposes.
-
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_69f224856d9881908c7f0dd64f059672 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f680d27d288190b66d52f002726551 |
completed | May 2, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:43 p.m.