Triple
T30084654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puer natus est nobis |
E764568
|
entity |
| Predicate | hasPlainchantCantusFirmus |
P183726
|
FINISHED |
| Object | Puer natus est nobis |
—
|
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: Puer natus est nobis | Statement: [Puer natus est nobis, hasPlainchantCantusFirmus, Puer natus est nobis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlainchantCantusFirmus Context triple: [Puer natus est nobis, hasPlainchantCantusFirmus, Puer natus est nobis]
-
A.
usesCantusFirmus
Indicates that one musical element is based on or incorporates a pre-existing cantus firmus melody as its structural foundation.
-
B.
hasCanticle
Indicates that an entity is associated with, contains, or is characterized by a specific canticle (a hymn or song of praise).
-
C.
usesChorale
Indicates that one entity incorporates or employs a chorale (a hymn-like musical piece) within its structure or content.
-
D.
hasChoralArrangement
Indicates that one entity is a choral arrangement version or setting of another entity (typically an original musical work).
-
E.
notableChant
Indicates that an entity is recognized for having a distinctive or significant chant associated with it.
- 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7a283388c81908e4a9ee3369e8d6f |
completed | May 3, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a224365081908ff6958e3b30bd05 |
completed | May 3, 2026, 7:29 p.m. |
Created at: April 29, 2026, 7:03 p.m.