Triple
T14952104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Janskerkhof |
E372819
|
entity |
| Predicate | hasSurroundingBuildingType |
P52857
|
FINISHED |
| Object | historic buildings |
—
|
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 buildings | Statement: [Janskerkhof, hasSurroundingBuildingType, historic buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurroundingBuildingType Context triple: [Janskerkhof, hasSurroundingBuildingType, historic buildings]
-
A.
hasNeighboringBuilding
Indicates that one building is located adjacent to or directly next to another building.
-
B.
hasBuildingStyleInSurroundings
chosen
Indicates that an entity is surrounded by or located in an area characterized by a particular building style.
-
C.
containsBuildingType
Indicates that a location or area includes at least one building of the specified type.
-
D.
containsBuilding
Indicates that one location or area includes a building within its boundaries.
-
E.
hasSurroundings
Indicates that an entity is located within or encircled by a particular environment, context, or set of surrounding elements.
- 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_69d85cca979481908747d2a81eba1cea |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded690f2e08190ad9dad6dc05a164a |
completed | April 15, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69de9a588c2c8190b1245a1c406f447c |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:39 a.m.