Triple
T38046789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The White Mosque |
E949638
|
entity |
| Predicate | courtyardSurface |
P189905
|
FINISHED |
| Object | stone paving |
—
|
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: stone paving | Statement: [The White Mosque, courtyardSurface, stone paving]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courtyardSurface Context triple: [The White Mosque, courtyardSurface, stone paving]
-
A.
hasCourtyardArea
Indicates that an entity includes or is associated with a courtyard and specifies the size or extent of that courtyard space.
-
B.
courtyardType
Indicates the specific kind or classification of a courtyard associated with an entity.
-
C.
courtyardShape
Indicates the geometric form or configuration that characterizes a courtyard.
-
D.
courtyardCapacity
Indicates the maximum number of entities that can be accommodated in a courtyard at the same time.
-
E.
hasCourtyard
Indicates that one entity includes, features, or is characterized by the presence of a courtyard.
- 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_69f76f000cf081908c11fb5443b392e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc44c7e73c819082d4fc1900fb9632 |
completed | May 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69fbc8efffbc8190a139798ad1880526 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fc44c67118819088accfeded7b449e |
completed | May 7, 2026, 7:52 a.m. |
Created at: May 3, 2026, 4:20 p.m.