Triple
T12070110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dulong–Petit law |
E287400
|
entity |
| Predicate | approximateFor |
P61091
|
FINISHED |
| Object | heavy metallic elements |
—
|
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: heavy metallic elements | Statement: [Dulong–Petit law, approximateFor, heavy metallic elements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateFor Context triple: [Dulong–Petit law, approximateFor, heavy metallic elements]
-
A.
approximates
Indicates that one entity is close to, but not exactly equal to, the value, form, or behavior of another entity.
-
B.
approximationType
Indicates the specific method or scheme used to approximate a value, function, or relationship in a given context.
-
C.
designedApproximately
Indicates that one entity was created, planned, or engineered to an estimated or imprecise degree in relation to another entity or specification.
-
D.
holdsApproximatelyFor
chosen
Indicates that a condition, relation, or value is valid only to an approximate degree or within a tolerance, rather than holding exactly.
-
E.
estimatedUsing
Indicates that one entity’s value, state, or outcome is derived by applying an estimation method, model, or procedure based on another entity.
- 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_69d6ab4846e081908ee7bbd66a6d3459 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bda47c8190b94860b31df4a98c |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:48 p.m.