Triple
T26138289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | معبد بتاح في منف |
E659441
|
entity |
| Predicate | كان من أهم |
P142639
|
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.
isOneOfMostImportantSeesIn
Indicates that something is regarded as one of the most significant or noteworthy sights or views within a particular place or context.
-
B.
importantObject
chosen
Indicates that one entity is considered especially significant, central, or of high priority in relation to another entity or context.
-
C.
isImportantFor
Indicates that something holds significant value, relevance, or necessity in relation to something else.
-
D.
importantInSect
Indicates that one entity holds significant importance, influence, or status within a particular sect or religious subgroup.
-
E.
importantAria
Indicates that an aria is considered significant or central in its musical, dramatic, or contextual role.
- 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.