Triple
T11129413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gospel of Thomas |
E263236
|
entity |
| Predicate | usedInScholarshipFor |
P6966
|
FINISHED |
| Object | study of historical Jesus |
—
|
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: study of historical Jesus | Statement: [Gospel of Thomas, usedInScholarshipFor, study of historical Jesus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInScholarshipFor Context triple: [Gospel of Thomas, usedInScholarshipFor, study of historical Jesus]
-
A.
scholarlyUse
chosen
Indicates that something is used for academic, educational, or research-related purposes.
-
B.
usedResearchFrom
Indicates that one entity based its work, findings, or outputs on research conducted or provided by another entity.
-
C.
usedInManuscripts
Indicates that something (such as a term, symbol, or feature) appears or is employed within one or more manuscripts.
-
D.
incorporatesRecentScholarship
Indicates that something (such as a work, argument, or analysis) includes and makes use of up-to-date academic research or findings.
-
E.
academicUse
Indicates that something is intended for, suitable for, or used within an academic or educational context.
- 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_69d6aa9c0ba08190bbd19c217489b755 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e830e804819097fcc3826d84dab8 |
completed | April 9, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69d7441efe948190ae4ab020121e169d |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:28 p.m.