Triple
T26635167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domplatz (Verden) |
E668614
|
entity |
| Predicate | nearbyBuildingType |
P75188
|
FINISHED |
| Object | historic townhouses |
—
|
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: historic townhouses | Statement: [Domplatz (Verden), nearbyBuildingType, historic townhouses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyBuildingType Context triple: [Domplatz (Verden), nearbyBuildingType, historic townhouses]
-
A.
buildingTypeAtCenter
Indicates that a specific type of building is located at the central position of a given area or spatial context.
-
B.
hasNearbyInfrastructureType
Indicates that an entity is located close to infrastructure of a specified type.
-
C.
nearbyFacilityType
chosen
Indicates that a facility of a specified type is located close to a given reference entity or location.
-
D.
hasNeighboringBuilding
Indicates that one building is located adjacent to or directly next to another building.
-
E.
buildingType
Indicates the specific category or function that characterizes what kind of building something is.
- 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_69ee9d0024b8819090a7c8cf669a3b6c |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 27, 2026, 2:26 a.m.