Triple
T33821145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Almoravid architecture |
E866828
|
entity |
| Predicate | styleOriginatesFrom |
P36679
|
FINISHED |
| Object | earlier Andalusi architecture |
—
|
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: earlier Andalusi architecture | Statement: [Almoravid architecture, styleOriginatesFrom, earlier Andalusi architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styleOriginatesFrom Context triple: [Almoravid architecture, styleOriginatesFrom, earlier Andalusi architecture]
-
A.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
-
B.
colorOrigin
Indicates the source or cause from which an entity’s color is derived or determined.
-
C.
causeOfOrigin
Indicates that one entity is the source or initiating cause from which another entity originates or comes into existence.
-
D.
hasDesignOrigin
chosen
Indicates that one entity is the source, inspiration, or original model from which the design of another entity is derived.
-
E.
describesOriginOf
Indicates that one entity specifies or explains the source, provenance, or origin of 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:46 a.m.