Triple
T18006341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Historia Hierosolymitana |
E430757
|
entity |
| Predicate | writtenByCleric |
P95657
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Historia Hierosolymitana, writtenByCleric, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenByCleric Context triple: [Historia Hierosolymitana, writtenByCleric, true]
-
A.
writtenByClergyOrTheologian
chosen
Indicates that the work or text was authored by a member of the clergy or a professional theologian.
-
B.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
-
C.
mainlyWrittenBy
Indicates that the primary authorship or main writing responsibility for something is attributed to a particular entity.
-
D.
foundedOnWritingsOf
Indicates that something (such as an idea, movement, or institution) is established or based upon the writings or written works of a particular source.
-
E.
writtenByCulture
Indicates that something (such as a text, work, or artifact) is authored, created, or produced by a particular culture or cultural group.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b51c7da48190ab70775a672e2d5f |
completed | April 19, 2026, 10:57 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:24 a.m.