Triple
T18772208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BD+31 643 |
E459041
|
entity |
| Predicate | hasHighMass |
P132903
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [BD+31 643, hasHighMass, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighMass Context triple: [BD+31 643, hasHighMass, yes]
-
A.
hasHigh
Indicates that an entity possesses a high level, degree, or intensity of a specified attribute or property.
-
B.
hasLowMass
Indicates that the subject possesses a relatively small amount of mass compared to a given standard or reference.
-
C.
hasMasses
Indicates that one entity possesses or is associated with one or more masses (quantities of matter).
-
D.
isMassive
Indicates that one entity has an extremely large size, scale, or extent relative to typical or comparable entities.
-
E.
hasHighStructure
Indicates that an entity possesses a high degree of organization, complexity, or well-defined internal structure in relation to another entity or standard.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e59336a6b08190819595a55177264e |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:52 a.m.