Triple
T28798064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulm postal region |
E727142
|
entity |
| Predicate | hasPrimarySortingCenter |
P90081
|
FINISHED |
| Object | Ulm mail center |
—
|
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: Ulm mail center | Statement: [Ulm postal region, hasPrimarySortingCenter, Ulm mail center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimarySortingCenter Context triple: [Ulm postal region, hasPrimarySortingCenter, Ulm mail center]
-
A.
hasSecondaryCenter
Indicates that an entity possesses an additional, subordinate or auxiliary center beyond its primary center.
-
B.
hasCenterOrder
Indicates that an entity has a central component or element arranged or organized in a specific order or sequence.
-
C.
hasRAndDCenterIn
Indicates that an entity maintains a research and development (R&D) center located in a specified place.
-
D.
hasPrimary
chosen
Indicates that one entity is designated as the main or most important instance (the primary) in relation to another entity.
-
E.
hasEarlyCenter
Indicates that an entity possesses or is associated with a primary focal point, hub, or center that occurs or is established earlier than others in time or sequence.
- 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69ff1d85441c8190931e758685a269f7 |
completed | May 9, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_69ff1d186cc48190b315c61e23de6551 |
completed | May 9, 2026, 11:40 a.m. |
Created at: April 28, 2026, 6:26 a.m.