Triple
T21353866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luca Fieschi |
E526559
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval churchman |
C16868
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: medieval churchman Context triple: [Luca Fieschi, instanceOf, medieval churchman]
-
A.
medieval clergyman
chosen
A medieval clergyman is a religious official of the Christian Church in the Middle Ages who performs spiritual duties, administers sacraments, and often serves as an educator and advisor within both religious and secular communities.
-
B.
medieval Christian monk
A medieval Christian monk is a religious man who lives in a monastic community under vows of poverty, chastity, and obedience, dedicating his life to prayer, work, and spiritual study within the Christian tradition.
-
C.
medieval church
A medieval church is a religious building from the Middle Ages, typically characterized by stone construction, vaulted ceilings, stained glass windows, and architectural styles such as Romanesque or Gothic, serving as a center for worship and community life.
-
D.
medieval Scottish churchman
A medieval Scottish churchman is a cleric or ecclesiastical leader in Scotland during the Middle Ages, involved in religious, political, and social affairs within the Church and broader society.
-
E.
Anglo-Norman cleric
An Anglo-Norman cleric is a religious official of the medieval Christian Church in England or Normandy after the Norman Conquest, typically involved in ecclesiastical administration, pastoral care, and the transmission of Latin learning within an Anglo-Norman cultural context.
- F. None of above.
Provenance (1 batch)
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_69e0b51cd5cc81909ac1187971e8a8ad |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 5:05 p.m.