Triple
T35184776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Our Lady of the Roses |
E1015954
|
entity |
| Predicate | hasAudioRecordingsOfMessages |
P193437
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Our Lady of the Roses, hasAudioRecordingsOfMessages, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAudioRecordingsOfMessages Context triple: [Our Lady of the Roses, hasAudioRecordingsOfMessages, yes]
-
A.
hasRecordedTexts
Indicates that there exist written or otherwise recorded textual materials documenting or produced by the subject entity.
-
B.
hasRecordingWith
Indicates that one entity is associated with or includes a particular recording as part of its content or representation.
-
C.
hasLiveRecordingFrom
Indicates that a live recording was made of something (e.g., a work, performance, or event) at or from a specified source, venue, or occasion.
-
D.
hasRecordingHistory
Indicates that an entity has an associated record of past recordings or recorded events.
-
E.
hasWorkRecordingsOn
Indicates that an entity has associated work recordings stored on or linked to another entity (such as a medium, platform, 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_69f76ddd815c8190b822eea06630f9fb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
| PDg | Predicate description generation | batch_69fd474a71648190b6b6ae4991db81b1 |
completed | May 8, 2026, 2:15 a.m. |
Created at: May 3, 2026, 4:02 p.m.