Triple
T5576305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akhmad Kadyrov Mosque |
E146326
|
entity |
| Predicate | complexCapacity |
P14460
|
FINISHED |
| Object | up to 100000 worshippers |
—
|
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: up to 100000 worshippers | Statement: [Akhmad Kadyrov Mosque, complexCapacity, up to 100000 worshippers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: complexCapacity Context triple: [Akhmad Kadyrov Mosque, complexCapacity, up to 100000 worshippers]
-
A.
totalCapacity
Indicates the maximum amount or volume that something can hold or accommodate in total.
-
B.
laterCapacity
Indicates that one entity’s capacity or capability occurs, becomes available, or is realized at a later time than another’s.
-
C.
maximumCapacity
chosen
Indicates the greatest allowable or designed amount of something that an entity can hold, contain, or handle.
-
D.
expandedCapacity
Indicates that an entity’s capacity has been increased beyond its previous or standard level.
-
E.
hasComplex
Indicates that one entity possesses, is associated with, or is part of a larger composite structure or complex formed 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_69c008ffed108190a084602227af6157 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020697fbc8190bd084d7896db3ab8 |
completed | March 22, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69c01b147cc081909237f3f2967d4cb8 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:37 p.m.