Triple
T36427546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juz 26 |
E897343
|
entity |
| Predicate | namedAfterOpeningWords |
P178820
|
FINISHED |
| Object | Thumma baddalnā |
—
|
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: Thumma baddalnā | Statement: [Juz 26, namedAfterOpeningWords, Thumma baddalnā]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedAfterOpeningWords Context triple: [Juz 26, namedAfterOpeningWords, Thumma baddalnā]
-
A.
namedAfter
Indicates that one entity has been given its name in honor of, or derived from, another entity.
-
B.
openingName
chosen
Indicates the name or title assigned to a specific opening, such as an initial move, phase, or starting configuration in a structured sequence or activity.
-
C.
hasOpeningNamedAfter
Indicates that an opening (such as in a game, work, or structure) is named after a particular entity.
-
D.
namedAfterLanguage
Indicates that one entity is named after a particular language.
-
E.
openingVerb
Indicates that an entity performs the initial or primary action that begins an event, process, or interaction.
- 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_69f76e559b10819099d6655a6e14587c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 3, 2026, 4:10 p.m.