Triple
T28119478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Couture-Saint-Germain |
E710736
|
entity |
| Predicate | postalCodeInBelgium |
P33952
|
FINISHED |
| Object | 1380 |
—
|
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: 1380 | Statement: [Couture-Saint-Germain, postalCodeInBelgium, 1380]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postalCodeInBelgium Context triple: [Couture-Saint-Germain, postalCodeInBelgium, 1380]
-
A.
positionInBelgium
Indicates that one entity occupies a specific geographic location within the territory of Belgium.
-
B.
tierInBelgium
Indicates that an entity belongs to, is classified within, or operates at a specific tier or level in the context of Belgium.
-
C.
passengerTrafficRankInBelgium
Indicates the relative position of an entity in terms of passenger traffic volume compared to other entities within Belgium.
-
D.
otherRegionsOfBelgium
Indicates that the related entities are regions of Belgium that are distinct from a specified primary Belgian region.
-
E.
postalCodeInCountry
chosen
Indicates that a given postal code is assigned to and valid within a particular country.
- 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_69ef9b72f63081909dfbc2c1ddae86c6 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 9:16 p.m.