Triple
T26138089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | منف |
E659435
|
entity |
| Predicate | كانت_مركز_عبادة |
P8490
|
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.
tookPlaceAtReligiousCenter
Indicates that an event or action occurred at a religious center or place of worship.
-
B.
ecclesiasticalCenter
Indicates that a place functions as a primary religious or church administrative hub for a surrounding area or community.
-
C.
isMajorReligiousBuildingOf
Indicates that a building serves as the primary or most significant religious structure associated with a particular religious group, institution, or area.
-
D.
hasMainAltarFor
Indicates that a specific altar serves as the primary or central altar designated for a particular entity, such as a church, chapel, or religious space.
-
E.
mainTemple
chosen
Indicates that one entity serves as the primary or central temple associated with 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_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 26, 2026, 8:18 p.m.