Triple
T12388556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tra le sollecitudini |
E295931
|
entity |
| Predicate | canonicalField |
P104697
|
FINISHED |
| Object | liturgical law |
—
|
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: liturgical law | Statement: [Tra le sollecitudini, canonicalField, liturgical law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canonicalField Context triple: [Tra le sollecitudini, canonicalField, liturgical law]
-
A.
emblematicField
Indicates that a particular field or attribute serves as a symbolic or representative marker for an entity or concept.
-
B.
primaryField
Indicates the main area of focus, discipline, or domain most centrally associated with an entity.
-
C.
canonicalText
Indicates that a standardized, authoritative textual representation is associated with an entity or expression.
-
D.
canonicalStatusIn
Indicates that something has a particular canonical or officially recognized status within a specified context or system.
-
E.
canonicalRole
Indicates that an entity holds a standard, primary, or officially recognized role within a particular context or system.
- 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_69d6ad9e653c8190b1473c860ee53dae |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d93fcf6aa8819080c9a2407a72db2e |
completed | April 10, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69d93ed256788190b704cad171a4824e |
completed | April 10, 2026, 6:17 p.m. |
| PDg | Predicate description generation | batch_69d93fa244148190a960be3ff6f1cf45 |
completed | April 10, 2026, 6:21 p.m. |
Created at: April 8, 2026, 9:54 p.m.