Triple
T35224181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Mosque of Algiers |
E1017043
|
entity |
| Predicate | hasMinaretShape |
P53930
|
FINISHED |
| Object | square minaret |
—
|
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: square minaret | Statement: [Great Mosque of Algiers, hasMinaretShape, square minaret]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMinaretShape Context triple: [Great Mosque of Algiers, hasMinaretShape, square minaret]
-
A.
hasMinaretLikeFeatures
Indicates that something possesses architectural characteristics resembling those of a minaret, such as a tall, slender tower-like form or similar structural features.
-
B.
hasMinaretFeature
Indicates that something possesses or includes a minaret as one of its architectural or structural features.
-
C.
minaretShape
chosen
Indicates that one entity has the specified architectural shape or form of a minaret in relation to another entity.
-
D.
hasMinaretType
Indicates that an entity possesses a minaret characterized by a specific architectural or structural type.
-
E.
hasPrayerHallShape
Indicates that an entity possesses a specific architectural or spatial form characteristic of a prayer hall.
- 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_69f76de072908190ab65038a8a7b6a79 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: May 3, 2026, 4:02 p.m.