Triple
T23310405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hymn of Praise |
E590566
|
entity |
| Predicate | hasSecondPartForm |
P151821
|
FINISHED |
| Object | cantata |
—
|
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: cantata | Statement: [Hymn of Praise, hasSecondPartForm, cantata]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondPartForm Context triple: [Hymn of Praise, hasSecondPartForm, cantata]
-
A.
hasTwoWordForm
Indicates that an entity is represented or expressed using a form consisting of exactly two words.
-
B.
hasSecondWordOfExpandedForm
Indicates that the second word in the fully expanded (non-abbreviated) form of one entity is related to or associated with another entity.
-
C.
hasSecond
Indicates that one entity is the second item, position, or element in an ordered sequence or pair relative to another entity.
-
D.
hasParticiple
Indicates that one entity is associated with the participle form (verbal adjective or non-finite verb form) of another entity.
-
E.
hasPartitiveMeaning
Indicates that the relationship expresses a partitive meaning, where one entity denotes a part or subset of the quantity, mass, or collection represented by another entity.
- 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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1972acad08190bb56541b822555cd |
completed | April 29, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d88b4ec8190a2a17a88e0eda178 |
completed | April 28, 2026, 2:38 a.m. |
Created at: April 17, 2026, 5:05 p.m.