Triple

T4371117
Position Surface form Disambiguated ID Type / Status
Subject Chronicle of Fulcher of Chartres E98897 entity
Predicate instanceOf P0 FINISHED
Object medieval Latin chronicle C12780 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 Latin chronicle
Context triple: [Chronicle of Fulcher of Chartres, instanceOf, medieval Latin chronicle]
  • A. medieval prose text
    A medieval prose text is a written work from the Middle Ages composed in continuous, non-verse form, often preserving narratives, religious teachings, legal codes, or historical accounts in the vernacular or Latin.
  • B. medieval literary work chosen
    A medieval literary work is a written or orally transmitted text from roughly the 5th to the 15th century that reflects the cultural, religious, and social contexts of the Middle Ages through genres such as epics, romances, hagiographies, chronicles, and lyric poetry.
  • C. Frankish historiography
    Frankish historiography is the body of historical writing produced in or about the Frankish realms, encompassing chronicles, annals, saints’ lives, and other narratives that construct and interpret the political, religious, and cultural history of the Franks from late antiquity through the early Middle Ages.
  • D. medievalist
    A medievalist is a scholar or enthusiast who studies and interprets the history, culture, literature, and societies of the Middle Ages.
  • E. medieval commentary
    A medieval commentary is a scholarly work from the Middle Ages that explains, interprets, and elaborates on an authoritative text, often blending exposition with theological, philosophical, or legal analysis.
  • 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_69b3454db3708190aeafd814413c4c3d completed March 12, 2026, 10:59 p.m.
Created at: March 12, 2026, 11:17 p.m.