Triple
T25869653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Church |
E651715
|
entity |
| Predicate | givesSpecialStatusTo |
P160946
|
FINISHED |
| Object | New Testament |
E13380
|
NE 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: New Testament | Statement: [New Church, givesSpecialStatusTo, New Testament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: givesSpecialStatusTo Context triple: [New Church, givesSpecialStatusTo, New Testament]
-
A.
givesSpecialStatusTo
chosen
Indicates that one entity confers a distinct or privileged status upon another entity.
-
B.
hadSpecialStatusIn
Indicates that an entity possessed a particular special, exceptional, or non-standard status within a specified context or time period.
-
C.
confersHonorificStatus
Indicates that one entity formally grants an honorific title, rank, or status to another entity.
-
D.
isSpecialAwardOf
Indicates that an award is a distinctive or exceptional honor specifically given to a particular entity (such as a person, work, or organization).
-
E.
grantedHonor
Indicates that one entity has formally bestowed an honor, award, or distinction upon another entity.
- F. None of above.
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_69e7ab3ad9d88190841ddcb93ab02e96 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f612607c388190ab61d1ac7d18e08d |
completed | May 2, 2026, 3:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a10da45a6388190b60196b83a9ac649 |
completed | May 22, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
Created at: April 22, 2026, 8:10 a.m.