Triple
T9834136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marburg (Lahn) station |
E239058
|
entity |
| Predicate | hasIbnr |
P90241
|
FINISHED |
| Object | 8000234 |
—
|
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: 8000234 | Statement: [Marburg (Lahn) station, hasIbnr, 8000234]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIbnr Context triple: [Marburg (Lahn) station, hasIbnr, 8000234]
-
A.
hasIbnrCode
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.
hasNationalIdentity
Indicates that an entity possesses or is associated with a particular national identity or nationality.
-
C.
ISBTNumber
Indicates that an entity is associated with, identified by, or assigned a specific ISBT (International Society of Blood Transfusion) number.
-
D.
hasInn
Indicates that one entity possesses, operates, or is associated with an inn as part of its facilities or properties.
-
E.
hasISIN
Indicates that a financial instrument is associated with a specific International Securities Identification Number (ISIN) that uniquely identifies it.
- 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_69ca84e314108190978324a4bdb959f8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3385054819094145c96204e3f0d |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e30bc08190816c0a6d29c21b0f |
completed | April 1, 2026, 11:39 a.m. |
| PDg | Predicate description generation | batch_69cd06abc9248190a506b64e9c516d03 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:32 p.m.