Triple
T16669322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yattendon Court |
E405064
|
entity |
| Predicate | hasArchitecturalCategory |
P63910
|
FINISHED |
| Object | domestic architecture |
—
|
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: domestic architecture | Statement: [Yattendon Court, hasArchitecturalCategory, domestic architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArchitecturalCategory Context triple: [Yattendon Court, hasArchitecturalCategory, domestic architecture]
-
A.
hasArchitecturalFeature
Indicates that one entity possesses, includes, or is characterized by a specific architectural feature or element.
-
B.
hasArchitecturalDiscipline
Indicates that one entity is associated with, practices, or specializes in a particular architectural discipline or field.
-
C.
hasArchitecturalPlanType
Indicates that an entity has or is associated with a specific type or category of architectural plan.
-
D.
hasArchitecturalMaterial
Indicates that something is constructed from, incorporates, or is characterized by a particular architectural material.
-
E.
hasArchType
chosen
Indicates that one entity possesses or is characterized by a particular architectural type or style.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37c9fa3d081909457b1bdea1d96e0 |
completed | April 18, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:18 a.m.