Triple
T26529058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vere languores nostros |
E670768
|
entity |
| Predicate | sungText |
P134835
|
FINISHED |
| Object | Vere languores nostros ipse tulit |
—
|
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: Vere languores nostros ipse tulit | Statement: [Vere languores nostros, sungText, Vere languores nostros ipse tulit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sungText Context triple: [Vere languores nostros, sungText, Vere languores nostros ipse tulit]
-
A.
sungIn
Indicates that something (such as a song, lyric, or performance) is performed vocally using a particular language, style, or vocal context.
-
B.
sungAs
Indicates that something is performed or vocalized in the manner, role, or identity specified by another entity (e.g., a song or part being sung as a particular character, style, or version).
-
C.
lyricText
chosen
Indicates that one entity is the lyrical content or words of a song or musical piece associated with another entity.
-
D.
textBy
Indicates that a given text or written content was authored or produced by a particular entity.
-
E.
vocalText
Indicates that an entity produces or is associated with spoken or sung textual content.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f613f5ec28819099ec679f636d61d9 |
completed | May 2, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:34 a.m.