Triple
T30295616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Architecture of the Prophet’s Mosque |
E770510
|
entity |
| Predicate | originalPlanType |
P8653
|
FINISHED |
| Object | rectangular courtyard mosque |
—
|
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: rectangular courtyard mosque | Statement: [Architecture of the Prophet’s Mosque, originalPlanType, rectangular courtyard mosque]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalPlanType Context triple: [Architecture of the Prophet’s Mosque, originalPlanType, rectangular courtyard mosque]
-
A.
originalPlan
Indicates that one entity is the initial or primary plan or intended course of action associated with another entity.
-
B.
planType
chosen
Indicates the specific category or kind of plan associated with an entity, such as its level, structure, or intended use.
-
C.
originalType
Indicates that one entity represents the initial or source type from which another entity is derived, transformed, or reclassified.
-
D.
planningRegimeType
Indicates the type or category of planning regime under which an action, process, or relationship is governed.
-
E.
originalPlanIncluded
Indicates that something was part of the initial or intended plan before any changes or revisions were made.
- 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00233e2170819084bee0c8f74cc1a4 |
completed | May 10, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_6a0022943fd08190b73007f080d5971d |
completed | May 10, 2026, 6:15 a.m. |
Created at: April 29, 2026, 7:48 p.m.