Triple
T2833986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Block 1B |
E62305
|
entity |
| Predicate | massComparedToBlock1 |
P37459
|
FINISHED |
| Object | heavier than SLS Block 1 |
—
|
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: heavier than SLS Block 1 | Statement: [Block 1B, massComparedToBlock1, heavier than SLS Block 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: massComparedToBlock1 Context triple: [Block 1B, massComparedToBlock1, heavier than SLS Block 1]
-
A.
isHeavierThan
chosen
Indicates that one entity has greater weight or mass than another entity.
-
B.
hasMass_kg
Indicates that an entity possesses a specific mass measured in kilograms.
-
C.
scaleComparison
Indicates a relationship where two or more entities are compared in terms of their size, magnitude, or scale relative to one another.
-
D.
givesMassTo
Indicates that one entity transfers or assigns a certain amount of mass to another entity.
-
E.
approximateMass
Indicates that one entity has a mass value that is an estimate or close approximation of the mass of another entity.
- 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_69ab4c3c39188190955b9c49d98463d8 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdec18b808190aedae2ed11d53b15 |
completed | March 7, 2026, 8:16 a.m. |
| PD | Predicate disambiguation | batch_69abdd0ce8b08190ba28c192988f38ce |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:01 p.m.