Triple
T29356499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frankfurt Rhine-Main |
E744456
|
entity |
| Predicate | europeanRegionCode |
P3446
|
FINISHED |
| Object | Rhine-Main metropolitan region |
—
|
NE NERFINISHED |
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: Rhine-Main metropolitan region | Statement: [Frankfurt Rhine-Main, europeanRegionCode, Rhine-Main metropolitan region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: europeanRegionCode Context triple: [Frankfurt Rhine-Main, europeanRegionCode, Rhine-Main metropolitan region]
-
A.
EUCountryCode
Indicates that an entity is identified by a country code belonging to a member state of the European Union.
-
B.
hasRegionCode
chosen
Indicates that an entity is associated with a specific regional identifier or code.
-
C.
NUTSRegionCode
Indicates the classification of an entity according to the NUTS (Nomenclature of Territorial Units for Statistics) regional coding system used for statistical regions.
-
D.
continentCode
Indicates the standardized code assigned to the continent with which an entity is associated.
-
E.
regionCodeType
Indicates the classification or format type used for a given region code within a coding or identification system.
- 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66984ecf48190bd8ccfcfee1c55af |
completed | May 2, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:12 p.m.