Triple
T26138177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | آثار معبد بتاح |
E659437
|
entity |
| Predicate | مكرّس لـ |
P1283
|
FINISHED |
| Object | الإله الحرفي والخالق بتاح |
—
|
NE NERFINISHED |
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.
dedicatedToConcept
Indicates that something is specifically devoted, committed, or purposefully directed toward a particular concept or abstract idea.
-
B.
dedicatedToBrand
Indicates that something (such as a resource, activity, or feature) is exclusively or primarily allocated or committed to a specific brand.
-
C.
oftenDedicatedTo
Indicates that something is frequently or habitually devoted, assigned, or committed to a particular purpose, activity, or recipient.
-
D.
dedicated
chosen
Indicates that one entity is formally assigned, reserved, or committed for the specific use, benefit, or purpose of another entity.
-
E.
dedicatedToCharacter
Indicates that something (such as a work, item, or effort) is formally devoted or addressed in honor of a specific character.
- 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_69f60be1d2408190820365bf7d8436bd |
completed | May 2, 2026, 2:36 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 8:18 p.m.