Triple
T18751421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LTB metric |
E458534
|
entity |
| Predicate | matterContent |
P82617
|
FINISHED |
| Object | pressureless dust |
—
|
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: pressureless dust | Statement: [LTB metric, matterContent, pressureless dust]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matterContent Context triple: [LTB metric, matterContent, pressureless dust]
-
A.
contentIs
Indicates that one entity serves as, or is equivalent to, the content contained within another entity.
-
B.
articleContent
Indicates that one entity is the textual or media content that makes up the body of another entity, typically an article or document.
-
C.
mainContentType
chosen
Indicates the primary type or category of content associated with an entity or resource.
-
D.
materialProvidedFor
Indicates that one entity supplies or makes available a material for use, processing, or incorporation by another entity or purpose.
-
E.
material
Indicates that one entity is physically composed of, made from, or constructed using the substance or material represented by the other 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e579ed4e6881908791f2a6250010a6 |
completed | April 20, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.