Triple
T2661513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Early Christians |
E54735
|
entity |
| Predicate | usedText |
P3129
|
FINISHED |
| Object | Hebrew Bible (Septuagint) as scripture |
—
|
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: Hebrew Bible (Septuagint) as scripture | Statement: [Early Christians, usedText, Hebrew Bible (Septuagint) as scripture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedText Context triple: [Early Christians, usedText, Hebrew Bible (Septuagint) as scripture]
-
A.
usedDocument
chosen
Indicates that one entity has employed, referenced, or otherwise made use of a particular document in performing an action or fulfilling a purpose.
-
B.
usedPhrase
Indicates that one entity employed or expressed a particular phrase in speech, writing, or another form of communication.
-
C.
usedTerm
Indicates that one entity employed, referenced, or applied a particular term in some context.
-
D.
usedToWrite
Indicates that one entity served as a tool, medium, or instrument that another entity employed to perform the act of writing.
-
E.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd9504d10819091abc03532a2fa6d |
completed | March 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.