Triple
T26062155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salah |
E657287
|
entity |
| Predicate | individualForm |
P160325
|
FINISHED |
| Object | individual prayer |
—
|
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: individual prayer | Statement: [Salah, individualForm, individual prayer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: individualForm Context triple: [Salah, individualForm, individual prayer]
-
A.
typicalForm
Indicates that one entity represents the standard, characteristic, or most common form or shape in which another entity typically appears or is realized.
-
B.
referenceForm
Indicates that one entity serves as a reference or canonical form for another entity, typically used as the standard or authoritative version to which others relate.
-
C.
filingForm
Indicates that an entity submits or completes a specific form or document, typically as part of an official or administrative process.
-
D.
keyIndividual
Indicates that an individual plays a central, influential, or otherwise critical role within a particular context, organization, or activity.
-
E.
helpedForm
Indicates that one entity contributed significantly to the creation, establishment, or founding of 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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f606941410819098a15b288273c3e1 |
completed | May 2, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f600be0de88190989611e952b03117 |
completed | May 2, 2026, 1:48 p.m. |
Created at: April 26, 2026, 7:18 p.m.