Triple

T15187795
Position Surface form Disambiguated ID Type / Status
Subject Verbandsgemeinde Rhein-Mosel E362921 entity
Predicate hasNumberOfLocalMunicipalities P30910 FINISHED
Object 18 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: 18 | Statement: [Verbandsgemeinde Rhein-Mosel, hasNumberOfLocalMunicipalities, 18]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNumberOfLocalMunicipalities
Context triple: [Verbandsgemeinde Rhein-Mosel, hasNumberOfLocalMunicipalities, 18]
  • A. hasNumberOfMunicipalities chosen
    Indicates the relationship that specifies how many municipalities are associated with or contained within a given administrative or geographic entity.
  • B. hasNumberOfLocalities
    Indicates the relationship that specifies how many localities (e.g., towns, districts, or similar administrative units) are associated with a given entity.
  • C. hasMunicipalPart
    Indicates that an administrative or territorial entity includes a municipality as one of its constituent parts.
  • D. hasNumberOfSubdistricts
    Indicates the relationship specifying how many subdistricts are associated with a given entity.
  • E. hasUrbanLocalities
    Indicates that an entity possesses or includes one or more urban localities within its jurisdiction or scope.
  • 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_69d85a09a39c81908759f23268e2d408 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e0067995fc8190b048f15086bd42f0 completed April 15, 2026, 9:43 p.m.
PD Predicate disambiguation batch_69deb97bd8bc8190b2ad4888f97cf963 completed April 14, 2026, 10:02 p.m.
Created at: April 10, 2026, 3:09 a.m.