Triple
T28693231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magnificat in D |
E729342
|
entity |
| Predicate | usesTextSource |
P131980
|
FINISHED |
| Object | Gospel of Luke |
—
|
NE NERFINISHED |
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: Gospel of Luke | Statement: [Magnificat in D, usesTextSource, Gospel of Luke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTextSource Context triple: [Magnificat in D, usesTextSource, Gospel of Luke]
-
A.
usesTextBy
Indicates that one entity makes use of or relies on a text authored or provided by another entity.
-
B.
typicalSourceText
Indicates that the related entity is a common or representative textual source from which information, examples, or data about another entity are typically drawn.
-
C.
textSources
chosen
Indicates that one entity serves as a source or origin for the text content associated with another entity.
-
D.
usesSourceType
Indicates that one entity makes use of, relies on, or operates based on a particular type or category of source.
-
E.
useText
Indicates that one entity employs or applies a specific text as a resource, tool, or content in performing an action or fulfilling a function.
- 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 28, 2026, 5:37 a.m.