Triple
T2840293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perpendicular Gothic |
E62448
|
entity |
| Predicate | vaultType |
P42957
|
FINISHED |
| Object | fan vault |
—
|
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: fan vault | Statement: [Perpendicular Gothic, vaultType, fan vault]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vaultType Context triple: [Perpendicular Gothic, vaultType, fan vault]
-
A.
securityType
Indicates the classification or category of security associated with an entity, such as the type of financial instrument, protection mechanism, or access control applied.
-
B.
keyType
Indicates the classification or category of a key in relation to how it is used or defined within a system or context.
-
C.
tressureType
Indicates the specific kind or category of tressure (a heraldic ornamental border around a shield or charge) associated with an entity.
-
D.
protectionType
Indicates the kind or method of protection that is applied to or associated with an entity.
-
E.
lockType
Indicates the specific kind or category of locking mechanism or access restriction applied to an entity or resource.
- 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_69ab4c3d16bc81908b3a1c98fbd287fe |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf15b7288190a03d1193cc0544a6 |
completed | March 7, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69abdd0ce8b08190ba28c192988f38ce |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abde4895dc819097c396c5d31ac1d1 |
completed | March 7, 2026, 8:14 a.m. |
Created at: March 6, 2026, 10:01 p.m.