Triple
T24763918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bronze |
E619527
|
entity |
| Predicate | hasTypicalTinContentRange |
P158108
|
FINISHED |
| Object | 5–25 percent by weight |
—
|
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: 5–25 percent by weight | Statement: [Bronze, hasTypicalTinContentRange, 5–25 percent by weight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalTinContentRange Context triple: [Bronze, hasTypicalTinContentRange, 5–25 percent by weight]
-
A.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
B.
hasTypicalCarbonContentRange
Indicates the usual lower and upper bounds of carbon content typically found in or associated with an entity.
-
C.
hasTypicalINRTargetRange
Indicates that there is a standard or commonly recommended INR (International Normalized Ratio) value range associated with a given therapy, condition, or clinical context.
-
D.
tieneRango
Indicates that one entity possesses, is assigned, or falls within a specific rank or range in relation to another entity.
-
E.
hasRangeCategory
Indicates that a property or measurement falls within a specified category or interval of possible values.
- 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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
| PDg | Predicate description generation | batch_69f464ae42e88190b3549fdf4e0b425e |
completed | May 1, 2026, 8:30 a.m. |
Created at: April 18, 2026, 4:28 a.m.