Triple
T23766492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adversus Noetum |
E587393
|
entity |
| Predicate | hasAttributedAuthor |
P4244
|
FINISHED |
| Object | Hippolytus of Rome |
—
|
NE NERFINISHED |
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: Hippolytus of Rome | Statement: [Adversus Noetum, hasAttributedAuthor, Hippolytus of Rome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAttributedAuthor Context triple: [Adversus Noetum, hasAttributedAuthor, Hippolytus of Rome]
-
A.
hasAuthor
chosen
Indicates that an entity is written or created by a specific author.
-
B.
hasAuthorOf
Indicates that one entity is the author or creator of another entity (such as a work, document, or publication).
-
C.
hasWorkAttributed
Indicates that a particular work or creation is credited or assigned as being produced by a specific agent or entity.
-
D.
hasContributorRoleOfAuthor
Indicates that an entity participates as a contributor specifically in the role of an author in relation to another entity.
-
E.
hasAlternativeAttribution
Indicates that an entity has another possible source, creator, or responsible party different from its primary or currently assigned attribution.
- 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_69e2490b8ac48190a6b35f1d5500486b |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c462ad348190b51bcaf66715a950 |
completed | April 29, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:15 p.m.