Triple
T4362729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Girobank |
E98697
|
entity |
| Predicate | establishedThrough |
P55783
|
FINISHED |
| Object | national 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: national postal system | Statement: [Girobank, establishedThrough, national postal system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedThrough Context triple: [Girobank, establishedThrough, national postal system]
-
A.
establishedFrom
Indicates that something was created, founded, or formed starting from a specified source, origin, or prior entity.
-
B.
establishedTo
Indicates that one entity was created, founded, or set up for the purpose of serving, supporting, or enabling another entity.
-
C.
establishedAs
Indicates that one entity is formally created, designated, or recognized in a particular role, status, or identity as another entity.
-
D.
establishedAt
Indicates the specific time or date at which something (such as an organization, system, or entity) was founded or brought into existence.
-
E.
establishedFollowing
Indicates that one entity created or set up another entity after, and in consequence of, a prior entity or event.
- F. None of above. chosen
Provenance (4 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_69b3454c772081908e20173e379e8ebe |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351e5ee308190a9271e73689b4a2b |
completed | March 12, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b34ff654308190b9717526120d80d3 |
completed | March 12, 2026, 11:44 p.m. |
Created at: March 12, 2026, 11:16 p.m.