Triple
T28632525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Welper |
E724681
|
entity |
| Predicate | sharesDialingCodeWith |
P106012
|
FINISHED |
| Object | Hattingen |
—
|
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: Hattingen | Statement: [Welper, sharesDialingCodeWith, Hattingen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesDialingCodeWith Context triple: [Welper, sharesDialingCodeWith, Hattingen]
-
A.
sharesAreaCode
chosen
Indicates that two entities have telephone numbers with the same area code.
-
B.
telephoneDialingCodeSystem
Indicates the telephone numbering or dialing code scheme used to place calls within or to a particular region, network, or service.
-
C.
callingCode
Indicates the telephone country or area code associated with an entity for making phone calls.
-
D.
sharesTelephonePartyLineWith
Indicates that two entities use the same shared telephone party line for their calls.
-
E.
continentCode
Indicates the standardized code assigned to the continent with which an entity is associated.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: April 28, 2026, 4:38 a.m.