Triple
T4493032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gödel metric |
E100623
|
entity |
| Predicate | hasMatterContent |
P22683
|
FINISHED |
| Object | pressureless dust with constant density |
—
|
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 with constant density | Statement: [Gödel metric, hasMatterContent, pressureless dust with constant density]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMatterContent Context triple: [Gödel metric, hasMatterContent, pressureless dust with constant density]
-
A.
hasMaterialType
Indicates that something is composed of, made from, or characterized by a specific type of material.
-
B.
hasContentFrom
chosen
Indicates that one entity’s content is derived from, includes, or is based on another entity.
-
C.
containsNewMaterial
Indicates that one entity includes or incorporates material that is newly created or not previously existing within another entity or context.
-
D.
hasMaterialOption
Indicates that an entity can be made from, or is available in, one or more alternative materials.
-
E.
hasMarginalia
Indicates that one entity (typically a document or page) contains marginal notes, comments, or annotations associated with it.
- 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_69bd43cdf15081909a4fa2585ff63b3e |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5570ba0881908f5fb4f8d0730e64 |
completed | March 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69bd5213e3d0819094b026989e686f01 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 12:59 p.m.