Triple
T2306846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Servant of the Servants of God |
E51858
|
entity |
| Predicate | scopeOfService |
P9961
|
FINISHED |
| Object | all the faithful |
—
|
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: all the faithful | Statement: [Servant of the Servants of God, scopeOfService, all the faithful]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scopeOfService Context triple: [Servant of the Servants of God, scopeOfService, all the faithful]
-
A.
scopeOfUse
Indicates the range, context, or conditions under which something is intended, allowed, or applicable to be used.
-
B.
scopeType
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
-
C.
scopeOfContribution
chosen
Indicates the specific area, domain, or extent within which an entity’s contribution or involvement applies.
-
D.
natureOfService
Indicates the specific type or category of service being provided or performed in a given context.
-
E.
sectorServed
Indicates the industry or economic sector that an entity primarily serves or targets with its activities, products, or services.
- 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_69a88b0bb30c81908ded03b006d29387 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abce1f4f0c8190a714e4dcb8449f7e |
completed | March 7, 2026, 7:05 a.m. |
| PD | Predicate disambiguation | batch_69abc58ce2a081908ce2f0cadd92e9f8 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.