Triple
T6311293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jordão |
E141506
|
entity |
| Predicate | hasPostalAddressWithin |
P16538
|
FINISHED |
| Object | Recife postal system |
—
|
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: Recife postal system | Statement: [Jordão, hasPostalAddressWithin, Recife postal system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPostalAddressWithin Context triple: [Jordão, hasPostalAddressWithin, Recife postal system]
-
A.
hasPostalAssociationWith
Indicates a relationship in which one entity is connected to another through postal services, such as mail handling, delivery, routing, or shared postal operations.
-
B.
hasPostalAddressComponent
Indicates that an entity is associated with a specific part or element of a postal address (such as street, city, or postal code).
-
C.
hasPostalRole
Indicates that an entity holds or is assigned a specific role or function within a postal or mail-related context.
-
D.
hasPostalAuthority
Indicates that an entity possesses official authority or jurisdiction over postal services or mail operations for a given area or context.
-
E.
hasPostalAddressRegion
chosen
Indicates the region component (such as state, province, or area) associated with an entity’s postal address.
- 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_69c008d00efc8190a36c05b4b4a3bf4b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0649d1e048190a3fc7fbce9d2ee57 |
completed | March 22, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69c060e311b48190b1c74a5cf9435623 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:28 p.m.