Triple
T1260961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 11 |
E12497
|
entity |
| Predicate | samplesReturnedMass |
P7301
|
FINISHED |
| Object | about 21.5 kilograms |
—
|
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: about 21.5 kilograms | Statement: [Apollo 11, samplesReturnedMass, about 21.5 kilograms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: samplesReturnedMass Context triple: [Apollo 11, samplesReturnedMass, about 21.5 kilograms]
-
A.
givesMassTo
Indicates that one entity transfers or assigns a certain amount of mass to another entity.
-
B.
approximateMass
chosen
Indicates that one entity has a mass value that is an estimate or close approximation of the mass of another entity.
-
C.
massParameter
Indicates a relationship where a specific mass value is assigned to or characterizes an entity as a parameter in a model or system.
-
D.
dryMass
Indicates the mass of an object excluding any contained fluids, propellants, or other consumable materials.
-
E.
fractionHeavierElementsByMass
Indicates the proportion of an object's total mass that is contributed by elements heavier than a specified reference element (often hydrogen or helium).
- 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_69a4933352e08190ac617291985e76c0 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bfc64e648190b9c4f980eb8168aa |
completed | March 1, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6eefbc81908dddd7d2ef368186 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:50 p.m.