Triple
T699801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Post Office Department |
E13972
|
entity |
| Predicate | typeOfAgency |
P3580
|
FINISHED |
| Object | postal administration |
—
|
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: postal administration | Statement: [Post Office Department, typeOfAgency, postal administration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAgency Context triple: [Post Office Department, typeOfAgency, postal administration]
-
A.
publicAgency
Indicates that an entity functions as a government-controlled or government-authorized organization that provides public services or carries out public administration.
-
B.
agency
Indicates that an entity acts on behalf of, represents, or exercises power or control for another entity in performing an action or fulfilling a role.
-
C.
organizationType
chosen
Indicates the specific category or classification of an organization in terms of its nature, structure, or primary function.
-
D.
hasTypeOfOrganization
Indicates that an entity is classified as belonging to a particular type or category of organization.
-
E.
hasOfficeType
Indicates that an entity’s office is classified as a specific type or category of office.
- 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a0de47f48190949bfa113330a404 |
completed | March 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69a49d265cf08190877f920d52a5ba43 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.