Triple
T3839557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laetare Medal |
E93417
|
entity |
| Predicate | awardingBodyReligiousAffiliation |
P45
|
FINISHED |
| Object | Catholic |
—
|
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: Catholic | Statement: [Laetare Medal, awardingBodyReligiousAffiliation, Catholic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awardingBodyReligiousAffiliation Context triple: [Laetare Medal, awardingBodyReligiousAffiliation, Catholic]
-
A.
religiousAffiliation
chosen
Indicates that one entity has a specified religious association, belief system, or denominational membership.
-
B.
hasReligiousOrganization
Indicates that an entity is associated with, governed by, or belongs to a specific religious organization.
-
C.
hasReligiousInstitutionType
Indicates that an entity is associated with, or classified by, a specific type of religious institution.
-
D.
declaredReligion
Indicates that an entity has formally stated or reported a particular religious affiliation.
-
E.
religiousAffiliationRequirement
Indicates that one entity requires another to have a specific religious affiliation as a condition for participation, membership, employment, or another form of involvement.
- 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_69aed96ce578819084ab16e3439976c9 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeeb9f305c8190b71ac53bbb0c4beb |
completed | March 9, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69aee74dcecc819098285483ec721b40 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:18 p.m.