Triple
T17515303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sacra Parallela |
E426552
|
entity |
| Predicate | hasAuthorAttributionStatus |
P7062
|
FINISHED |
| Object | disputed authorship |
—
|
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: disputed authorship | Statement: [Sacra Parallela, hasAuthorAttributionStatus, disputed authorship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorAttributionStatus Context triple: [Sacra Parallela, hasAuthorAttributionStatus, disputed authorship]
-
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.
authorStatus
Indicates the role or standing an individual holds as an author, such as their level of contribution, recognition, or current authorship state in relation to a work.
-
C.
hasAuthor
Indicates that an entity is written or created by a specific author.
-
D.
hasAuthorInCatalog
Indicates that an item in a catalog is associated with a specific author recorded in that catalog.
-
E.
hasAuthorNote
Indicates that an entity includes or is associated with a specific author-provided note or commentary.
- 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4525fa0c48190b42b36c40db7ed7f |
completed | April 19, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f5fbcc8190a6ea9639bf5650da |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.