Triple
T18415822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Old Town Hall of Amsterdam |
E441884
|
entity |
| Predicate | depictsBuildingFunction |
P125859
|
FINISHED |
| Object | civic building |
—
|
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: civic building | Statement: [The Old Town Hall of Amsterdam, depictsBuildingFunction, civic building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depictsBuildingFunction Context triple: [The Old Town Hall of Amsterdam, depictsBuildingFunction, civic building]
-
A.
depictsBuildingType
chosen
Indicates that one entity visually represents or portrays a specific type or category of building associated with another entity.
-
B.
describesBuilding
Indicates that one entity provides a description or characterization of a building entity.
-
C.
depictsFormerBuilding
Indicates that an image or representation shows a building that no longer exists in its depicted form or function.
-
D.
functionInBuilding
Indicates that a specific function, role, or use is carried out within a particular building.
-
E.
featuresBuilding
Indicates that one entity includes or incorporates a building as a notable component or characteristic.
- 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_69d8b9eb8a508190a942fd75ebd8b1dc |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e51a278fdc8190aa81a2ade682d942 |
completed | April 19, 2026, 6:08 p.m. |
| PD | Predicate disambiguation | batch_69e469bf7f74819096a01173493412c2 |
completed | April 19, 2026, 5:35 a.m. |
Created at: April 10, 2026, 10:47 a.m.