Triple
T18499228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duecento |
E452023
|
entity |
| Predicate | hasNotablePoeticForm |
P30317
|
FINISHED |
| Object | sonnet |
—
|
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: sonnet | Statement: [Duecento, hasNotablePoeticForm, sonnet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotablePoeticForm Context triple: [Duecento, hasNotablePoeticForm, sonnet]
-
A.
hasLyricalForm
Indicates that one entity (typically a musical or poetic work) possesses or is characterized by a particular lyrical structure or form.
-
B.
hasPoeticLyrics
Indicates that something (such as a song, text, or speech) contains lyrics or wording that are artistic, expressive, or characteristic of poetry.
-
C.
hasPoeticDevice
Indicates that one entity (typically a text or passage) employs or contains a specific poetic device present in the other entity.
-
D.
poeticStructure
chosen
Indicates a relationship where one entity defines, embodies, or specifies the formal poetic organization (such as meter, rhyme scheme, or stanza pattern) used by another entity.
-
E.
hasFeatureInPoem
Indicates that a poem includes or is characterized by a particular feature, element, or attribute.
- 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e532c3810c81908fa329c177c6d96c |
completed | April 19, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:36 a.m.