Triple
T21031696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pseudo-Isidorean Decretals |
E518077
|
entity |
| Predicate | identifiedAsForgeryBy |
P63298
|
FINISHED |
| Object | early modern scholars |
—
|
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: early modern scholars | Statement: [Pseudo-Isidorean Decretals, identifiedAsForgeryBy, early modern scholars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifiedAsForgeryBy Context triple: [Pseudo-Isidorean Decretals, identifiedAsForgeryBy, early modern scholars]
-
A.
exposedAsForgeryWork
chosen
Indicates that a work has been revealed or officially determined to be a forgery rather than an authentic piece.
-
B.
isSubjectToCounterfeiting
Indicates that something is vulnerable to being illegally imitated, forged, or reproduced in order to deceive.
-
C.
forgeryProbability
Indicates the likelihood that an item, document, or representation is forged or not authentic.
-
D.
isFabricated
Indicates that something has been artificially made, constructed, or invented rather than naturally occurring or genuinely existing.
-
E.
isAuthentic
Indicates that something is genuine, real, or true to its claimed origin, nature, or standard.
- 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_69e0b503275c8190afd9a163f997c709 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc82b5348190b449d59e6cada9de |
completed | April 21, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf6728881908a2a43a5c8804a2a |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:55 p.m.