Triple
T17606055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decree Frequens |
E428833
|
entity |
| Predicate | authoredCollectivelyBy |
P23019
|
FINISHED |
| Object | fathers of the Council of Constance |
—
|
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: fathers of the Council of Constance | Statement: [Decree Frequens, authoredCollectivelyBy, fathers of the Council of Constance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authoredCollectivelyBy Context triple: [Decree Frequens, authoredCollectivelyBy, fathers of the Council of Constance]
-
A.
authorCollective
chosen
Indicates that a work is created or authored by a collective group rather than by an individual.
-
B.
coAuthorAlsoWrote
Indicates that a person who is a co-author of one work also wrote another work, linking shared authorship across multiple creations.
-
C.
hasCoauthor
Indicates that two or more entities have jointly authored the same work or publication.
-
D.
publishedInCollaborationWith
Indicates that an entity was published as a result of a joint effort or partnership with another entity.
-
E.
hasCollaboratedIn
Indicates that two or more entities have worked together on a shared project, task, or activity.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46c4c06a88190a0be2dec3d6056c4 |
completed | April 19, 2026, 5:46 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:51 a.m.