Triple
T9219157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norman architecture |
E221314
|
entity |
| Predicate | typicalStructuralElement |
P86921
|
FINISHED |
| Object | round arch |
—
|
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: round arch | Statement: [Norman architecture, typicalStructuralElement, round arch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStructuralElement Context triple: [Norman architecture, typicalStructuralElement, round arch]
-
A.
designedStructureType
Indicates the type or category of structure that something has been specifically designed to be.
-
B.
superstructureType
Indicates the specific kind or design category of a structure’s superstructure that an entity possesses or is associated with.
-
C.
integratedStructure
Indicates that multiple components are combined into a single, cohesive structure that functions as an integrated whole.
-
D.
typicalTopology
Indicates the usual or most common network or structural arrangement that characterizes how the related entities are organized or interconnected.
-
E.
buildingStructure
Indicates that one entity is a structural component or physical part that forms, supports, or constitutes the construction of another entity.
- 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_69ca83eae42c8190a0ea9e040710a277 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccda730f688190b64b2cc8c4898ac3 |
completed | April 1, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69cc660ce23c81909c7bbe10f4a05f36 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc687067fc81909da2d78fda0cdcfb |
completed | April 1, 2026, 12:36 a.m. |
Created at: March 30, 2026, 7:28 p.m.