Triple
T34649589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Front |
E889797
|
entity |
| Predicate | isFacadeOf |
P124555
|
FINISHED |
| Object | country house |
—
|
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: country house | Statement: [West Front, isFacadeOf, country house]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFacadeOf Context triple: [West Front, isFacadeOf, country house]
-
A.
facadeFeature
Indicates that one element functions as a distinct architectural or design feature on the façade of another structure.
-
B.
hasFacadeSystem
Indicates that one entity possesses or is equipped with a particular façade system as part of its structure or design.
-
C.
formsFacadeOf
chosen
Indicates that one entity serves as the outward-facing surface or front (facade) of another entity, typically concealing or enclosing it.
-
D.
hasFacadeBy
Indicates that one entity’s façade (front-facing exterior surface) is designed, created, or provided by another entity.
-
E.
façadeRole
Indicates that one entity functions as a façade or front-facing interface that represents, conceals, or simplifies access to another underlying entity or system.
- 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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f722c1bc648190a79bfdc722dcaaa4 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:04 a.m.