Triple
T26138468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tahmid |
E659447
|
entity |
| Predicate | primaryPhrase |
P66408
|
FINISHED |
| Object | al-ḥamdu lillāh |
—
|
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: al-ḥamdu lillāh | Statement: [Tahmid, primaryPhrase, al-ḥamdu lillāh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryPhrase Context triple: [Tahmid, primaryPhrase, al-ḥamdu lillāh]
-
A.
mainPhrase
chosen
Indicates that the referenced phrase functions as the primary or central phrase within a larger linguistic or structural unit.
-
B.
primaryFor
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
-
C.
primarySingle
Indicates that an entity has exactly one main or primary association of the specified type, with no additional concurrent primary associations.
-
D.
primaryName
Indicates that the associated name is the main or most commonly used name for the entity in question.
-
E.
primaryFront
Indicates that one entity serves as the main or most important front-facing side or surface in relation to another entity.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: April 26, 2026, 8:18 p.m.