Triple
T31594965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pontifical commission |
E806195
|
entity |
| Predicate | scopeCanBe |
P25607
|
FINISHED |
| Object | doctrinal issues |
—
|
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: doctrinal issues | Statement: [pontifical commission, scopeCanBe, doctrinal issues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scopeCanBe Context triple: [pontifical commission, scopeCanBe, doctrinal issues]
-
A.
scopeDefinedBy
Indicates that the extent or boundaries of one entity’s applicability, influence, or validity are determined or constrained by another entity.
-
B.
scopeType
chosen
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
-
C.
scopeDoesNotInclude
Indicates that a given scope explicitly excludes or does not cover a particular element, condition, or responsibility.
-
D.
scopeOfControl
Indicates the extent or range within which an entity has authority, influence, or control over another entity or set of entities.
-
E.
scopeCondition
Indicates the specific conditions or constraints under which something is valid, applicable, or in effect within a given scope.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a83460188190a201e67b786198a4 |
completed | May 3, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:30 p.m.