Triple
T21935918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sicán culture |
E541686
|
entity |
| Predicate | metalwork |
P26314
|
FINISHED |
| Object | gold alloys |
—
|
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: gold alloys | Statement: [Sicán culture, metalwork, gold alloys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metalwork Context triple: [Sicán culture, metalwork, gold alloys]
-
A.
allMetalConstruction
Indicates that something is constructed entirely or almost entirely from metal components.
-
B.
associatedMetal
chosen
Indicates a relationship where one entity is linked or connected to a particular metal, such as by composition, usage, origin, or symbolic association.
-
C.
mainMetalProduced
Indicates that a location, facility, or process primarily produces a particular metal as its main output.
-
D.
stateMetal
Indicates that an entity is in a metallic state or exhibits properties characteristic of a metal.
-
E.
metalComparedWith
Indicates a comparison being made between two metals in terms of some property, quality, or characteristic.
- 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_69e0c47e2e5c81909a7f74ce3de50911 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f124048fe48190987340d5a6945176 |
completed | April 28, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:53 p.m.