Triple
T2864370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artemis IV |
E63401
|
entity |
| Predicate | scienceObjective |
P7242
|
FINISHED |
| Object | support lunar science investigations |
—
|
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: support lunar science investigations | Statement: [Artemis IV, scienceObjective, support lunar science investigations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scienceObjective Context triple: [Artemis IV, scienceObjective, support lunar science investigations]
-
A.
scienceGoals
chosen
Indicates the objectives or intended outcomes that guide and justify a scientific activity, project, or investigation.
-
B.
educationalObjective
Indicates the intended learning goal, skill, or competency that an educational resource, activity, or program is designed to achieve.
-
C.
isScientific
Indicates that something pertains to or is based on systematic scientific methods, principles, or knowledge.
-
D.
expeditionObjective
Indicates the primary goal or purpose that an expedition is intended to achieve.
-
E.
testObjective
Indicates that an entity serves as the goal, purpose, or intended outcome of a test or testing activity.
- 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_69ab4c42fb8c8190b36e161d47c03b81 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdfb853908190aa2fd492e9fa5e87 |
completed | March 7, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69abdd123ec48190af50a1859aea50b7 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.