Triple
T33839823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apennine Front |
E867327
|
entity |
| Predicate | hasRelationToMission |
P60884
|
FINISHED |
| Object | primary geological target of Apollo 15 EVAs |
—
|
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: primary geological target of Apollo 15 EVAs | Statement: [Apennine Front, hasRelationToMission, primary geological target of Apollo 15 EVAs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelationToMission Context triple: [Apennine Front, hasRelationToMission, primary geological target of Apollo 15 EVAs]
-
A.
isTargetOfMission
chosen
Indicates that an entity is the intended objective or focus of a particular mission or operation.
-
B.
hasMissionIn
Indicates that an entity carries out, undertakes, or is assigned a mission within a specified location or region.
-
C.
containsMission
Indicates that one entity includes or encompasses a mission as part of its contents, scope, or responsibilities.
-
D.
hasMissionTo
Indicates that an entity is assigned or dedicated to carrying out a specific mission, task, or purpose related to another entity or objective.
-
E.
relatedMission
Indicates that one mission is connected or associated with another mission in a meaningful way, such as by shared goals, context, participants, or timeline.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:47 a.m.