Triple
T4086409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Jack Horner |
E87594
|
entity |
| Predicate | rhymeType |
P31675
|
FINISHED |
| Object | traditional nursery rhyme |
—
|
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: traditional nursery rhyme | Statement: [Little Jack Horner, rhymeType, traditional nursery rhyme]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rhymeType Context triple: [Little Jack Horner, rhymeType, traditional nursery rhyme]
-
A.
hasRhymeStyle
Indicates that two linguistic elements share the same pattern or style of rhyming.
-
B.
rhymeScheme
Indicates the pattern of end sounds in a sequence of lines, showing which lines rhyme with each other.
-
C.
hasTraditionalRhyme
chosen
Indicates that something is associated with or characterized by a conventional or culturally established rhyme.
-
D.
poeticStructure
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.
lyricalPhrase
Indicates that one entity is a lyrical phrase or line that is part of, derived from, or associated with another entity such as a song, poem, or musical work.
- 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_69aed94425148190be337845d56fac22 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc7ceeb48190807f0f5078ccfa12 |
completed | March 9, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69aef909c9c88190b09d48dad325a83c |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.