Triple
T518391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Letter to the Hebrews |
E10758
|
entity |
| Predicate | authorshipDebate |
P7062
|
FINISHED |
| Object | attributed by some to Paul |
—
|
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: attributed by some to Paul | Statement: [Letter to the Hebrews, authorshipDebate, attributed by some to Paul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorshipDebate Context triple: [Letter to the Hebrews, authorshipDebate, attributed by some to Paul]
-
A.
authorshipStatus
chosen
Indicates the current state or condition of an entity’s role as an author in relation to a work (e.g., confirmed, disputed, anonymous, or pending).
-
B.
traditionalAuthorship
Indicates that an entity is recognized as the conventional or historically accepted author of a work, according to traditional attribution.
-
C.
probableAuthorOf
Indicates that an entity is likely, but not certainly, the author or creator of another entity.
-
D.
hasAuthor
Indicates that an entity is written or created by a specific author.
-
E.
mayAuthor
Indicates that an entity has the potential or permission to be the author of another entity (such as a work or document).
- 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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f19ee6748190916603ef3a9e27f3 |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f0151e8c81909a82b58ac0515eba |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.