Triple
T28722534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P46 |
E730132
|
entity |
| Predicate | religiousWorkType |
P193831
|
FINISHED |
| Object | Christian scripture manuscript |
—
|
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 scripture manuscript | Statement: [P46, religiousWorkType, Christian scripture manuscript]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousWorkType Context triple: [P46, religiousWorkType, Christian scripture manuscript]
-
A.
religiousServiceType
Indicates the specific kind or category of religious service associated with an event or context.
-
B.
religiousMovementType
Indicates the specific kind or category of religious movement with which an entity is associated.
-
C.
religiousActivity
Indicates participation in, performance of, or association with practices, rituals, or behaviors related to a religion or faith tradition.
-
D.
religiousSupportType
Indicates the type or form of support provided or received in a religious or faith-based context.
-
E.
ecclesiasticalType
Indicates the specific ecclesiastical category or classification that applies to a religious entity within a church hierarchy.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
| PDg | Predicate description generation | batch_69fd57b9cdec81908536c4159e375931 |
completed | May 8, 2026, 3:25 a.m. |
Created at: April 28, 2026, 5:54 a.m.