Triple
T30941187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hameln-Pyrmont district |
E788263
|
entity |
| Predicate | hasTownFamousFor |
P2813
|
FINISHED |
| Object | Pied Piper of Hamelin legend |
—
|
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: Pied Piper of Hamelin legend | Statement: [Hameln-Pyrmont district, hasTownFamousFor, Pied Piper of Hamelin legend]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTownFamousFor Context triple: [Hameln-Pyrmont district, hasTownFamousFor, Pied Piper of Hamelin legend]
-
A.
isInTownKnownFor
Indicates that one entity is located in a town that is notable or distinguished for the other entity.
-
B.
inscriptionFamousFor
Indicates that an inscription is widely recognized or notable specifically because of the referenced feature, event, content, or characteristic.
-
C.
hasFamousCity
chosen
Indicates that an entity possesses or is associated with a city that is widely recognized or renowned.
-
D.
primaryCityLandmarkOf
Indicates that a landmark is a principal or defining landmark associated with a specific city.
-
E.
isBorneByNotablePeopleIn
Indicates that something (such as a name, title, or attribute) is carried or held by notable people within a specified place or context.
- 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_69f224c180f88190ad177372ee02b7e2 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 29, 2026, 8:53 p.m.