Triple
T14901700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jadis et naguère |
E360019
|
entity |
| Predicate | hasPoeticFeatures |
P60474
|
FINISHED |
| Object | musical rhythm |
—
|
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: musical rhythm | Statement: [Jadis et naguère, hasPoeticFeatures, musical rhythm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPoeticFeatures Context triple: [Jadis et naguère, hasPoeticFeatures, musical rhythm]
-
A.
hasPoeticLyrics
Indicates that something (such as a song, text, or speech) contains lyrics or wording that are artistic, expressive, or characteristic of poetry.
-
B.
hasPoeticDevice
chosen
Indicates that one entity (typically a text or passage) employs or contains a specific poetic device present in the other entity.
-
C.
hasPoeticVoice
Indicates that one entity possesses or exhibits the distinctive poetic style, tone, or expressive voice associated with another entity.
-
D.
hasLyricalForm
Indicates that one entity (typically a musical or poetic work) possesses or is characterized by a particular lyrical structure or form.
-
E.
hasPoeticEpigraphs
Indicates that one entity (typically a work) includes poetic epigraphs associated with or prefacing another entity.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded609bf68819099ca3aa3fe1acadc |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a4a14a88190951bb8f4c60bd37b |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:11 a.m.