Triple
T9355949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | copper |
E225137
|
entity |
| Predicate | isUsedForArtAndArchitecture |
P84366
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [copper, isUsedForArtAndArchitecture, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedForArtAndArchitecture Context triple: [copper, isUsedForArtAndArchitecture, true]
-
A.
hasArtHistoricalSignificance
Indicates that something holds notable importance or influence within the context of art history.
-
B.
hasCulturalSignificanceFor
Indicates that something holds particular cultural meaning, value, or importance for a specified group or community.
-
C.
hasArtOrMemorial
Indicates that one entity possesses, contains, or is associated with a work of art or a memorial related to another entity.
-
D.
artStyleOfEnclosingSculpture
Indicates that one entity specifies the artistic style or aesthetic category of a surrounding or enclosing sculpture associated with another entity.
-
E.
artUse
chosen
Indicates that one entity uses, applies, or employs another entity within an artistic or creative context.
- 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_69ca842abfd48190949d71c3b86eeba8 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd4fee9d4c8190a7d121c9487ccca2 |
completed | April 1, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69cc7a68ab9481909f97cb70764697cc |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:42 p.m.