Triple
T6336009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlin Hauptbahnhof |
E142491
|
entity |
| Predicate | IbnrCode |
P37973
|
FINISHED |
| Object | 8011160 |
—
|
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: 8011160 | Statement: [Berlin Hauptbahnhof, IbnrCode, 8011160]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IbnrCode Context triple: [Berlin Hauptbahnhof, IbnrCode, 8011160]
-
A.
hasIbnrCode
chosen
Indicates that an entity is associated with a specific incurred-but-not-reported (IBNR) code used to classify or track unreported insurance-related obligations.
-
B.
inseeCode
Indicates the official INSEE (French national statistics institute) code assigned to an entity, typically identifying a specific geographic or administrative unit.
-
C.
ICCCode
Indicates that an entity is associated with a specific International Criminal Court (ICC) code, identifying its classification or legal reference under ICC standards.
-
D.
numericCode
Indicates that an entity is associated with a specific numerical identifier or classification code.
-
E.
nrcLicenseNumber
Indicates that an entity is associated with a specific license number issued by the U.S. Nuclear Regulatory Commission (NRC).
- 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_69c008d4d8e88190ad301c05b08722ac |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0654a88a881908d5cb2aa7f22c4c7 |
completed | March 22, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69c060e7e2d48190af9d004236466788 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:30 p.m.