Triple
T10993865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Entrance Hymn (Eisodikon) |
E259813
|
entity |
| Predicate | mayBeChantedIn |
P38181
|
FINISHED |
| Object | different Byzantine echoi (modes) |
—
|
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: different Byzantine echoi (modes) | Statement: [Entrance Hymn (Eisodikon), mayBeChantedIn, different Byzantine echoi (modes)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeChantedIn Context triple: [Entrance Hymn (Eisodikon), mayBeChantedIn, different Byzantine echoi (modes)]
-
A.
alsoChantedIn
chosen
Indicates that a chant, hymn, or recitation is performed or used in an additional context, location, or tradition beyond its primary one.
-
B.
hasChant
Indicates that an entity is associated with or characterized by a particular chant.
-
C.
chantingIs24x7
Indicates that the chanting activity occurs continuously, 24 hours a day, 7 days a week.
-
D.
languageOfChant
Indicates the language in which a chant is performed or expressed.
-
E.
spokenIncantation
Indicates that an entity has uttered a specific magical or ritual phrase, typically to invoke an effect or power.
- 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_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. |
Created at: April 8, 2026, 9:24 p.m.