Triple
T2433636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Young's modulus |
E52901
|
entity |
| Predicate | typicalValueForConcrete |
P33135
|
FINISHED |
| Object | about 20–40 GPa |
—
|
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: about 20–40 GPa | Statement: [Young's modulus, typicalValueForConcrete, about 20–40 GPa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalValueForConcrete Context triple: [Young's modulus, typicalValueForConcrete, about 20–40 GPa]
-
A.
exactValueReason
Indicates that the value is specified exactly as given due to a particular justification or rationale.
-
B.
associatedValue
chosen
Indicates that one entity is linked to another entity that serves as its corresponding or contextually related value.
-
C.
isValuedFor
Indicates that one entity is appreciated, esteemed, or considered important because of a particular quality, contribution, or characteristic it provides to another entity.
-
D.
hasCommonValue
Indicates that two or more entities share at least one identical value or attribute in common.
-
E.
hasApproximateValue
Indicates that one entity’s value is close to, but not exactly equal to, the value of another entity within an acceptable margin of error.
- 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_69ab4959bcc0819083246f9fb10439e3 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcc74a5108190a3a9631b0cc1a127 |
completed | March 7, 2026, 6:57 a.m. |
| PD | Predicate disambiguation | batch_69abc5aa1b60819081b87f7985c6cff3 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 6, 2026, 9:43 p.m.