Triple
T4661786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lemaître–Tolman metric |
E102548
|
entity |
| Predicate | hasEnergyMomentumContent |
P58272
|
FINISHED |
| Object | 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: dust | Statement: [Lemaître–Tolman metric, hasEnergyMomentumContent, dust]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnergyMomentumContent Context triple: [Lemaître–Tolman metric, hasEnergyMomentumContent, dust]
-
A.
hasRestEnergy
Indicates that an entity possesses intrinsic energy associated with its mass when at rest, independent of its motion or external forces.
-
B.
hasCenterOfMassMomentum
Indicates that one entity possesses or is characterized by a specific value of momentum associated with its center of mass.
-
C.
hasRestMass
Indicates that an entity possesses a non-zero invariant mass when measured in its own rest frame.
-
D.
hasEnergyRole
Indicates that one entity plays a specific functional role in the production, distribution, management, or use of energy in relation to another entity.
-
E.
hasConservedQuantity
Indicates that a system or process possesses a quantity that remains constant (is conserved) throughout its evolution or interactions.
- 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_69bd43d823288190952279faa0d1d066 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd632b7fb88190821f213620719d6b |
completed | March 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69bd62126b0c81909ba3f21b21e30d54 |
completed | March 20, 2026, 3:04 p.m. |
| PDg | Predicate description generation | batch_69bd631328fc81909b28ae0a2a3ed9bb |
completed | March 20, 2026, 3:09 p.m. |
Created at: March 20, 2026, 1:15 p.m.