Triple
T24307927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | القدوس |
E612583
|
entity |
| Predicate | يُذكر في سياق |
P118237
|
FINISHED |
| Object | تسبيح الله |
—
|
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: تسبيح الله | Statement: [القدوس, يُذكر في سياق, تسبيح الله]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: يُذكر في سياق Context triple: [القدوس, يُذكر في سياق, تسبيح الله]
-
A.
contextOf
Indicates that one entity provides the situational, informational, or environmental background within which another entity exists, occurs, or is interpreted.
-
B.
locatedInNationalContext
Indicates that an entity exists or occurs within the geographical, political, or cultural boundaries of a specific nation.
-
C.
appearsInContextWith
chosen
Indicates that two entities are observed or used together within the same situational, textual, or usage context.
-
D.
wroteInContextOf
Indicates that an entity authored or composed something within, or specifically influenced by, a particular context, situation, or set of circumstances.
-
E.
context
Indicates that one entity provides the surrounding circumstances, setting, or background within which another entity, event, or statement occurs or is interpreted.
- 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_69e2d7d91bb48190bc5377d17a85fb21 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2922821248190a1b274f839251ddc |
completed | April 29, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 1:31 a.m.