Triple
T697150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jama Masjid, Delhi |
E13917
|
entity |
| Predicate | courtyardCapacity |
P16753
|
FINISHED |
| Object | about 25000 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: about 25000 worshippers | Statement: [Jama Masjid, Delhi, courtyardCapacity, about 25000 worshippers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courtyardCapacity Context triple: [Jama Masjid, Delhi, courtyardCapacity, about 25000 worshippers]
-
A.
hasCourtyard
Indicates that one entity includes, features, or is characterized by the presence of a courtyard.
-
B.
seatingCapacity
Indicates the maximum number of people that something (typically a venue or vehicle) is designed or allowed to seat.
-
C.
numberOfMainCourtyards
Indicates the quantity of primary courtyards associated with an entity.
-
D.
numberOfHalls
Indicates the quantity of halls associated with a given entity or location.
-
E.
typicalCapacity
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
- F. None of above. chosen
Provenance (4 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a0c8055881909565ebde2be8fd7a |
completed | March 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69a49d2586b081908e052cc5ba1d2685 |
completed | March 1, 2026, 8:10 p.m. |
| PDg | Predicate description generation | batch_69a49dc20880819085fa60dc1851f9dc |
completed | March 1, 2026, 8:12 p.m. |
Created at: March 1, 2026, 7:36 p.m.