Triple
T24404854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mariatown |
E615282
|
entity |
| Predicate | hasPostalAuthorityCountryCode |
P17984
|
FINISHED |
| Object | CA |
—
|
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: CA | Statement: [Mariatown, hasPostalAuthorityCountryCode, CA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPostalAuthorityCountryCode Context triple: [Mariatown, hasPostalAuthorityCountryCode, CA]
-
A.
hasPostalCountryCode
chosen
Indicates that an entity is associated with a specific country code used for postal addressing or mail routing.
-
B.
hasPostalAdministrationCountry
Indicates that a postal administration is under the jurisdiction of, or officially associated with, a particular country.
-
C.
hasPostalAuthority
Indicates that an entity possesses official authority or jurisdiction over postal services or mail operations for a given area or context.
-
D.
hasPostalSystem
Indicates that an entity possesses or operates an organized system for sending, receiving, and delivering mail or parcels.
-
E.
hasPostalSystemOf
Indicates that one entity possesses, uses, or is characterized by the postal system belonging to another entity.
- 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_69e2d7e780bc81908049c779e697a7f6 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f294de76848190bd2cf3c7add2dcf1 |
completed | April 29, 2026, 11:31 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:05 a.m.