Triple
T28867071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christ the Lord: Out of Egypt |
E729028
|
entity |
| Predicate | authorReturnTo |
P184369
|
FINISHED |
| Object | Christian faith themes |
—
|
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: Christian faith themes | Statement: [Christ the Lord: Out of Egypt, authorReturnTo, Christian faith themes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorReturnTo Context triple: [Christ the Lord: Out of Egypt, authorReturnTo, Christian faith themes]
-
A.
authorBelongsTo
Indicates that an author is affiliated with, or is a member of, a particular organization, group, or entity.
-
B.
canonicalAuthor
Indicates that an entity is the officially recognized or standard author of a given work or resource.
-
C.
authorType
Indicates the specific role or category of authorship associated with an entity, such as primary author, co-author, or editor.
-
D.
authorStatus
Indicates the role or standing an individual holds as an author, such as their level of contribution, recognition, or current authorship state in relation to a work.
-
E.
authorOrigin
Indicates that an author has a specific place, region, or country as their origin or background.
- F. None of above. chosen
Provenance (4 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7b0e3917481908a394680d76743c3 |
completed | May 3, 2026, 8:32 p.m. |
Created at: April 28, 2026, 6:49 a.m.