Triple
T23463623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antiquorum habet fida relatio |
E569046
|
entity |
| Predicate | hasCanonicalTopic |
P152370
|
FINISHED |
| Object | indulgences |
—
|
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: indulgences | Statement: [Antiquorum habet fida relatio, hasCanonicalTopic, indulgences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanonicalTopic Context triple: [Antiquorum habet fida relatio, hasCanonicalTopic, indulgences]
-
A.
hasCanonicalCategory
Indicates that something is associated with its standard or officially recognized category within a classification system.
-
B.
hasCanonicalTerm
Indicates that one term in a set is designated as the standard or authoritative form used to represent a concept or entity.
-
C.
hasTopicType
Indicates that something is associated with, or categorized under, a particular type of topic.
-
D.
hasCanonicalRelevance
Indicates that something is considered standard, authoritative, or centrally important within an established canon or reference framework.
-
E.
hasCanonicalContext
Indicates that something is associated with its primary, standard, or officially recognized contextual setting or framework.
- F. None of above. chosen
Provenance (4 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_69e2458ebd808190b3298163132cfb0b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a69f0a54819084c19c248a572253 |
completed | April 29, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:54 p.m.