Triple
T388994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praedicate Evangelium |
E8840
|
entity |
| Predicate | belongsToGenre |
P8464
|
FINISHED |
| Object | canonical legislation |
—
|
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: canonical legislation | Statement: [Praedicate Evangelium, belongsToGenre, canonical legislation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToGenre Context triple: [Praedicate Evangelium, belongsToGenre, canonical legislation]
-
A.
hasGenreStrength
Indicates that something possesses a particular intensity or degree of emphasis associated with a specific genre.
-
B.
genusIncludes
Indicates that a particular genus contains or encompasses the specified subordinate taxonomic entities (such as species or subspecies).
-
C.
genreDiversity
Indicates the extent to which an entity involves, includes, or spans multiple distinct genres rather than being confined to a single genre.
-
D.
knownForMusicGenre
Indicates that an entity is recognized or notable for producing, performing, or being associated with a particular music genre.
-
E.
hasArtisticGenre
chosen
Indicates that an entity (such as a work or creation) belongs to or is characterized by a particular artistic genre.
- 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_69a2e7f55c60819097aff65ea2ca2832 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec5988708190aa86d9460cecf050 |
completed | Feb. 28, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69a2e96960608190bdd342da9c5ddb5e |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.