Triple
T3710339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Philip and St James Church in Sękowa |
E81394
|
entity |
| Predicate | buildingStructure |
P50946
|
FINISHED |
| Object | timber-framed structure |
—
|
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: timber-framed structure | Statement: [St Philip and St James Church in Sękowa, buildingStructure, timber-framed structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingStructure Context triple: [St Philip and St James Church in Sękowa, buildingStructure, timber-framed structure]
-
A.
buildingComplex
Indicates a relationship where multiple buildings are grouped and function together as a single integrated complex.
-
B.
buildingSection
Indicates a relationship where one entity is a specific section, part, or subdivision of a larger building.
-
C.
building
Indicates that one entity constructs, assembles, or develops another entity, typically over a period of time.
-
D.
buildingSystem
Indicates that one entity functions as a system, subsystem, or organized set of components that serves or supports the operation of a building.
-
E.
buildingShape
Indicates the geometric form or outline that characterizes a building’s overall structure.
- F. None of above. chosen
Provenance (4 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_69ad8b1a81588190b3f27a5483bb610e |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adc584b86c8190ba1a1073da440b07 |
completed | March 8, 2026, 6:52 p.m. |
| PD | Predicate disambiguation | batch_69adc041a8608190a2d543dab6d2ef6c |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc133ef50819094c2b971f31f1615 |
completed | March 8, 2026, 6:34 p.m. |
Created at: March 8, 2026, 3:33 p.m.