Triple
T10501710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genesis Rock |
E247687
|
entity |
| Predicate | collectedByMissionType |
P94500
|
FINISHED |
| Object | crewed lunar landing mission |
—
|
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: crewed lunar landing mission | Statement: [Genesis Rock, collectedByMissionType, crewed lunar landing mission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectedByMissionType Context triple: [Genesis Rock, collectedByMissionType, crewed lunar landing mission]
-
A.
typeOfMission
Indicates the specific category or nature of a mission that an entity is associated with or engaged in.
-
B.
observedByMission
Indicates that an event, object, or phenomenon was detected, recorded, or monitored by a specific mission.
-
C.
usedByMission
Indicates that something (such as a resource, tool, or method) is utilized or employed in the execution of a particular mission.
-
D.
overseesMissionType
Indicates that one entity has responsibility for supervising or managing a particular type or category of mission carried out by another entity.
-
E.
capturesMissionOf
Indicates that one entity records, represents, or encapsulates the mission or overarching purpose of another entity.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5099b797c8190a94803fa94eb6981 |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8e24ac8190912c9f11b8bd3084 |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe46a6448190b061bc3545835cad |
completed | April 7, 2026, 12:53 p.m. |
Created at: April 6, 2026, 12:25 p.m.