Triple
T13125749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gold |
E311837
|
entity |
| Predicate | commonAlloyName |
P108186
|
FINISHED |
| Object | white gold |
—
|
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: white gold | Statement: [Gold, commonAlloyName, white gold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonAlloyName Context triple: [Gold, commonAlloyName, white gold]
-
A.
associatedMetal
Indicates a relationship where one entity is linked or connected to a particular metal, such as by composition, usage, origin, or symbolic association.
-
B.
typicalValueForAluminum
Indicates the standard or commonly accepted value (such as a property or parameter) that is characteristic for aluminum in a given context.
-
C.
allMetalConstruction
Indicates that something is constructed entirely or almost entirely from metal components.
-
D.
mainMetalProduced
Indicates that a location, facility, or process primarily produces a particular metal as its main output.
-
E.
metalComparedWith
Indicates a comparison being made between two metals in terms of some property, quality, or characteristic.
- F. None of above. chosen
Provenance (4 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9819946808190b41335fb1054accd |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98043a74c81908648e6cd0b4c7f71 |
completed | April 10, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d98134df64819084a5674f9475dcc2 |
completed | April 10, 2026, 11:01 p.m. |
Created at: April 9, 2026, 9:07 p.m.