Triple
T19421309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City Hall of Franeker |
E485859
|
entity |
| Predicate | hasFacadeCharacteristic |
P274
|
FINISHED |
| Object | ornate façade |
—
|
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: ornate façade | Statement: [City Hall of Franeker, hasFacadeCharacteristic, ornate façade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFacadeCharacteristic Context triple: [City Hall of Franeker, hasFacadeCharacteristic, ornate façade]
-
A.
hasFacadeSystem
Indicates that one entity possesses or is equipped with a particular façade system as part of its structure or design.
-
B.
facadeFeature
Indicates that one element functions as a distinct architectural or design feature on the façade of another structure.
-
C.
hasCharacteristic
chosen
Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
-
D.
hasFacadeOrganization
Indicates that one organization functions as a façade or front for another organization, concealing the latter’s true role or identity.
-
E.
hasFacadeColorAssociation
Indicates an association between a building’s facade and a specific color or set of colors used on it.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63214d768819082129100d7116521 |
completed | April 20, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.