Triple
T16445869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abbey of Saint-Pierre de Moissac |
E399422
|
entity |
| Predicate | hasCloisterCapitals |
P17704
|
FINISHED |
| Object | biblical scenes |
—
|
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: biblical scenes | Statement: [Abbey of Saint-Pierre de Moissac, hasCloisterCapitals, biblical scenes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCloisterCapitals Context triple: [Abbey of Saint-Pierre de Moissac, hasCloisterCapitals, biblical scenes]
-
A.
hasCloister
chosen
Indicates that one entity possesses or includes a cloister as part of its structure or layout.
-
B.
hasCloisterFromCentury
Indicates that an entity possesses a cloister that dates from, or was constructed in, a specified century.
-
C.
hasCloisterWalls
Indicates that something possesses or is surrounded by cloister walls as an architectural feature.
-
D.
hasCuria
Indicates that an entity possesses, is associated with, or is served by a specific curia (council, court, or governing body).
-
E.
cloisterStyle
Indicates the architectural style or design characteristics of a cloister in relation to a building or site.
- 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32cdb5d908190bb6c5cb3c794cf4b |
completed | April 18, 2026, 7:03 a.m. |
| PD | Predicate disambiguation | batch_69e227048d608190a4205eae3117629a |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.