Triple
T30248502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mengen |
E769126
|
entity |
| Predicate | hasHistoricTownRights |
P195087
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mengen, hasHistoricTownRights, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricTownRights Context triple: [Mengen, hasHistoricTownRights, true]
-
A.
containsHistoricTown
Indicates that one entity geographically includes or encompasses a town that has recognized historical significance.
-
B.
governsHistoricTown
Indicates that one entity exercises official governing authority over a town that is recognized as historically significant.
-
C.
hasMarketTownHistory
Indicates that an entity has a historical association with functioning as a market town or possessing recognized market-town status in the past.
-
D.
hasCastleTownHistory
Indicates that an entity has a historical association with a castle town, such as originating from, being located in, or significantly shaped by one.
-
E.
hasHistoricTownSquare
Indicates that an entity possesses or includes a town square that is of historical significance.
- 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_69f224831dc08190b2e569b987264057 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
| PDg | Predicate description generation | batch_69fda4fe67a08190bdaa84ceabd6de6c |
completed | May 8, 2026, 8:55 a.m. |
Created at: April 29, 2026, 7:40 p.m.