Triple
T26138297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | معبد بتاح في منف |
E659441
|
entity |
| Predicate | كان جزءًا من |
P52847
|
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.
containedPartOf
Indicates that one entity is physically or logically included within and forms a part of another entity.
-
B.
usedToBePartOf
Indicates that an entity was formerly a component or member of another entity but is no longer part of it.
-
C.
implementedAsPartOf
Indicates that something has been realized or carried out as a component or subset of a larger implementation or project.
-
D.
consideredPartOf
chosen
Indicates that one entity is regarded or treated as a component, segment, or subset of another entity within a larger whole.
-
E.
builtAsPartOf
Indicates that one entity was constructed as a component or subset of a larger, encompassing entity or project.
- 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_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:18 p.m.