Triple
T4531576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dysnomia |
E106309
|
entity |
| Predicate | systemMassConstraint |
P49586
|
FINISHED |
| Object | used to determine mass of Eris |
—
|
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: used to determine mass of Eris | Statement: [Dysnomia, systemMassConstraint, used to determine mass of Eris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemMassConstraint Context triple: [Dysnomia, systemMassConstraint, used to determine mass of Eris]
-
A.
designedToConstrain
chosen
Indicates that one entity is intentionally created or configured to limit, restrict, or control the behavior, range, or properties of another entity.
-
B.
hasCenterOfMassMomentum
Indicates that one entity possesses or is characterized by a specific value of momentum associated with its center of mass.
-
C.
givesMassTo
Indicates that one entity transfers or assigns a certain amount of mass to another entity.
-
D.
collisionSystem
Indicates a physical interaction where two or more entities impact or collide with each other within a defined system or environment.
-
E.
hasMass_kg
Indicates that an entity possesses a specific mass measured in kilograms.
- 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_69bd43f3d6e08190a91824f833d51bbe |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd579d7a88819083eb0620ca176f2e |
completed | March 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69bd521edd00819099dfccaa65dddd61 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:03 p.m.