Triple
T9756540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OPAL opacity project |
E236566
|
entity |
| Predicate | compositionParameter |
P90824
|
FINISHED |
| Object | hydrogen mass fraction |
—
|
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: hydrogen mass fraction | Statement: [OPAL opacity project, compositionParameter, hydrogen mass fraction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compositionParameter Context triple: [OPAL opacity project, compositionParameter, hydrogen mass fraction]
-
A.
compositionMethod
Indicates the technique or process by which something is composed, created, or constructed.
-
B.
compositionStyle
Indicates the characteristic manner or approach in which something is composed, such as its structural, aesthetic, or stylistic conventions.
-
C.
compositionRule
Indicates how multiple elements or components are combined or arranged according to a specific rule or pattern.
-
D.
compositionDetail
Indicates that one entity specifies or describes the internal makeup, structure, or constituent elements of another entity.
-
E.
compositionForm
Indicates the structural or organizational form in which something is composed or arranged.
- 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_69ca84d4eddc8190996fec1417d2bae8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9fb2889481908fba4a449d5007fe |
completed | April 1, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69cd03d0772c8190bd1750cf1cfba309 |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd081a9c5c819093439be7e802ff85 |
completed | April 1, 2026, 11:57 a.m. |
Created at: March 30, 2026, 8:24 p.m.