Triple
T28928551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lützel |
E733717
|
entity |
| Predicate | hasNeighbourhoodRelation |
P75079
|
FINISHED |
| Object | Neuendorf |
—
|
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: Neuendorf | Statement: [Lützel, hasNeighbourhoodRelation, Neuendorf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeighbourhoodRelation Context triple: [Lützel, hasNeighbourhoodRelation, Neuendorf]
-
A.
hasNeighborRelationshipWith
chosen
Indicates that one entity is located adjacent to or directly next to another entity, sharing a neighbor relationship.
-
B.
hasNeighbourhood
Indicates that one entity is located within, or is associated with, a particular neighborhood area of another entity.
-
C.
hasMunicipalRelationshipWith
Indicates a formal or functional connection between two municipalities, such as cooperation, partnership, or administrative association.
-
D.
hasNeighborhoodRole
Indicates that an entity holds a specific role, function, or position within a neighborhood or local community context.
-
E.
hasNeighbourhoodStatus
Indicates that an entity has a particular status, classification, or condition specifically in relation to a given neighbourhood.
- 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_69f05b0b49b08190b8994b339c7980f6 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: April 28, 2026, 8:25 a.m.