Triple
T15898352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steel |
E385520
|
entity |
| Predicate | hasTypicalDensity |
P2023
|
FINISHED |
| Object | Approximately 7.8 g/cm³ |
—
|
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: Approximately 7.8 g/cm³ | Statement: [Steel, hasTypicalDensity, Approximately 7.8 g/cm³]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalDensity Context triple: [Steel, hasTypicalDensity, Approximately 7.8 g/cm³]
-
A.
hasMeanDensity
chosen
Indicates that one entity possesses a specified average mass per unit volume (mean density).
-
B.
typicalUnionDensity
Indicates the usual or characteristic level of labor union membership or representation within a given group, sector, or region.
-
C.
hasHighDensityOf
Indicates that one entity contains or exhibits a large concentration or amount of another entity within a given area, volume, or context.
-
D.
hasCentralDensity
Indicates that an entity possesses a specified value for its density at the central or core region.
-
E.
hasDensityParameter
Indicates that an entity is associated with a specific density-related parameter or value used to characterize its density properties.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142ca3b208190946c3aa4c1e6087c |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:51 a.m.