Triple
T30355244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alhambra tilings |
E772124
|
entity |
| Predicate | foundInPartOf |
P36747
|
FINISHED |
| Object | Court of the Lions |
—
|
NE NERFINISHED |
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: Court of the Lions | Statement: [Alhambra tilings, foundInPartOf, Court of the Lions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundInPartOf Context triple: [Alhambra tilings, foundInPartOf, Court of the Lions]
-
A.
hasPartIn
Indicates that an entity participates in or plays a role within a larger event, process, or composite entity.
-
B.
discoveredAsPartOf
chosen
Indicates that something was found, identified, or revealed in the course of a larger activity, process, or investigation of which it formed a component.
-
C.
containedPartOf
Indicates that one entity is physically or logically included within and forms a part of another entity.
-
D.
usedInPartOf
Indicates that something is utilized or plays a functional role within a specific component or subpart of a larger whole.
-
E.
foundInStructure
Indicates that an entity is located within, contained by, or structurally part of another entity or structure.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: April 29, 2026, 7:56 p.m.