Triple
T3453028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Mosque of Córdoba |
E72834
|
entity |
| Predicate | centralNaveAdded |
P48305
|
FINISHED |
| Object | 16th century |
—
|
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: 16th century | Statement: [Great Mosque of Córdoba, centralNaveAdded, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralNaveAdded Context triple: [Great Mosque of Córdoba, centralNaveAdded, 16th century]
-
A.
centralIn
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
B.
centralLocation
Indicates that one entity serves as the primary or central place associated with another entity.
-
C.
centralBranch
Indicates that one entity functions as the main or primary branch within a larger organizational or structural system relative to another entity.
-
D.
centralWork
Indicates that a particular work is the primary, most important, or focal work associated with an entity or context.
-
E.
centralPlinthHeight
Indicates the height of a central plinth relative to a defined reference or surrounding elements.
- 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_69ad85b12a908190a1d10a6b03b4f8ae |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbaa2f5ec81909ced93c01e8fe38b |
completed | March 8, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69adae041d588190a84a02bca94adec8 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adaed74ecc8190b74dc70ab59a3e1c |
completed | March 8, 2026, 5:16 p.m. |
Created at: March 8, 2026, 3:16 p.m.