Triple
T37672047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book of Amun-Ra |
E937987
|
entity |
| Predicate | propDesign |
P1529
|
FINISHED |
| Object | ornate metal pages |
—
|
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: ornate metal pages | Statement: [Book of Amun-Ra, propDesign, ornate metal pages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propDesign Context triple: [Book of Amun-Ra, propDesign, ornate metal pages]
-
A.
projectionDesignBy
Indicates that a projection or projected visual element is created or designed by a particular agent or designer.
-
B.
hasDesign
chosen
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
C.
designsFor
Indicates that one entity creates or plans something specifically intended to serve, suit, or be used by another entity.
-
D.
productTypeDesigned
Indicates that one entity is the type or category of product for which another entity has been specifically designed.
-
E.
designDescription
Indicates that an entity has a textual explanation or summary of its design, structure, or intended configuration.
- 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_69f76ed7b1408190ba8c93c53cb8becf |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba9e6be1c8190ad03baea7b8d76d0 |
completed | May 6, 2026, 8:51 p.m. |
| PD | Predicate disambiguation | batch_69fba887821c8190ae93ef1dd389e9c8 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.