Triple
T5853782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chapel of St John the Evangelist |
E130099
|
entity |
| Predicate | hasVault |
P43372
|
FINISHED |
| Object | barrel vault over nave |
—
|
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: barrel vault over nave | Statement: [Chapel of St John the Evangelist, hasVault, barrel vault over nave]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVault Context triple: [Chapel of St John the Evangelist, hasVault, barrel vault over nave]
-
A.
hasVaultType
chosen
Indicates that an entity is associated with or classified by a particular type or category of vault.
-
B.
hasGoldVault
Indicates that one entity possesses or contains a vault specifically used for storing gold.
-
C.
vaultType
Indicates the specific category or classification of a vault associated with an entity or transaction.
-
D.
hasPin
Indicates that one entity possesses, includes, or is equipped with a specific pin (such as a connector pin, security PIN, or fastening pin).
-
E.
hasPortal
Indicates that one entity possesses or provides access to a portal connecting to another location or entity.
- 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_69c0084de39081909eb34e6bed74215a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03345ca0c819081c81148d054fed2 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:55 p.m.