Triple
T4835313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centaurus A/M83 Group |
E108043
|
entity |
| Predicate | hasMassApprox |
P7301
|
FINISHED |
| Object | on the order of 10^13 solar masses (group scale) |
—
|
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: on the order of 10^13 solar masses (group scale) | Statement: [Centaurus A/M83 Group, hasMassApprox, on the order of 10^13 solar masses (group scale)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMassApprox Context triple: [Centaurus A/M83 Group, hasMassApprox, on the order of 10^13 solar masses (group scale)]
-
A.
approximateMass
chosen
Indicates that one entity has a mass value that is an estimate or close approximation of the mass of another entity.
-
B.
hasMass_kg
Indicates that an entity possesses a specific mass measured in kilograms.
-
C.
givesMassTo
Indicates that one entity transfers or assigns a certain amount of mass to another entity.
-
D.
isMassive
Indicates that one entity has an extremely large size, scale, or extent relative to typical or comparable entities.
-
E.
hasRestMass
Indicates that an entity possesses a non-zero invariant mass when measured in its own rest frame.
- 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_69bd43fbe444819085cb970706ef73f7 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c21c7f08190846049d31fdfa144 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:25 p.m.