Triple
T8202088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nobitz |
E191601
|
entity |
| Predicate | isLocalAdministrativeCommunity |
P81476
|
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: [Nobitz, isLocalAdministrativeCommunity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocalAdministrativeCommunity Context triple: [Nobitz, isLocalAdministrativeCommunity, true]
-
A.
hasLocalGovernmentCommunity
Indicates that one entity possesses or is associated with a community-level local government authority responsible for administering that area.
-
B.
isCommunityOf
Indicates that one entity functions as a community composed of, or defined by, the members or elements represented by the other entity.
-
C.
isCentralLocalityOf
Indicates that a locality serves as the main or central place within a larger administrative or geographic area.
-
D.
isMunicipal
Indicates that something belongs to, is administered by, or is characteristic of a municipality or local city government.
-
E.
hasLocalCommunities
Indicates that an entity is associated with or contains smaller, localized community groups within a specific area or region.
- 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_69ca82c7f3e08190857bf1fc63b2a10c |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb5df84b108190b4407a72a3500af9 |
completed | March 31, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69cb36aac86081909b83636e352e0ced |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb46635424819085d086972b264280 |
completed | March 31, 2026, 3:58 a.m. |
Created at: March 30, 2026, 5:43 p.m.