Triple
T33731843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 16 landing site |
E864293
|
entity |
| Predicate | sampleMassReturnedKg |
P54856
|
FINISHED |
| Object | 95.8 |
—
|
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: 95.8 | Statement: [Apollo 16 landing site, sampleMassReturnedKg, 95.8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sampleMassReturnedKg Context triple: [Apollo 16 landing site, sampleMassReturnedKg, 95.8]
-
A.
returnedSampleMass
chosen
Indicates that a specified amount of mass was brought back or retrieved as a sample from a source or mission.
-
B.
hasMass_kg
Indicates that an entity possesses a specific mass measured in kilograms.
-
C.
returnCargoMass
Indicates the mass of cargo that is brought back or returned from a mission, trip, or transport operation.
-
D.
cargoMassDelivered
Indicates that a certain mass of cargo has been successfully transported and delivered from a source to a destination.
-
E.
givesMassTo
Indicates that one entity transfers or assigns a certain amount of mass to 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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:44 a.m.