Triple
T10993861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Entrance Hymn (Eisodikon) |
E259813
|
entity |
| Predicate | hasVariantText |
P96537
|
FINISHED |
| Object | festal entrance hymn |
—
|
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: festal entrance hymn | Statement: [Entrance Hymn (Eisodikon), hasVariantText, festal entrance hymn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVariantText Context triple: [Entrance Hymn (Eisodikon), hasVariantText, festal entrance hymn]
-
A.
hasVariant
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
B.
hasVariantSystem
Indicates that one system is an alternative or variant form of another system within the same general framework or category.
-
C.
hasVariantGroup
Indicates that an entity is associated with a specific group of related variants that share common characteristics or classification.
-
D.
hasVariantFamily
Indicates that one entity is related to another as a different version, type, or family variant of it.
-
E.
hasVariantSeries
Indicates a relationship where one entity is a variant or alternative series derived from or associated with another series.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d795d460d88190bff918d6dfdb0f93 |
completed | April 9, 2026, 12:04 p.m. |
| PD | Predicate disambiguation | batch_69d72e93ac648190b46c5d12bf3eb1e9 |
completed | April 9, 2026, 4:44 a.m. |
| PDg | Predicate description generation | batch_69d732242fdc8190be77d1f730a42935 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:24 p.m.