Triple
T2833933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artemis II |
E62304
|
entity |
| Predicate | launchStatus |
P42903
|
FINISHED |
| Object | planned |
—
|
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: planned | Statement: [Artemis II, launchStatus, planned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchStatus Context triple: [Artemis II, launchStatus, planned]
-
A.
launchOutcome
Indicates the result or consequence of a launch event, such as whether it succeeded, failed, or had a specific status or outcome.
-
B.
trainingStatus
Indicates the current state or phase of an entity within a training or learning process.
-
C.
launchRecord
Indicates the act of initiating or starting a recorded instance of a process, event, or operation.
-
D.
laterStatus
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
-
E.
automationStatus
Indicates whether a process, task, or system is being performed automatically or requires manual intervention.
- 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_69ab4c3c39188190955b9c49d98463d8 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdec18b808190aedae2ed11d53b15 |
completed | March 7, 2026, 8:16 a.m. |
| PD | Predicate disambiguation | batch_69abdd0ce8b08190ba28c192988f38ce |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abde4895dc819097c396c5d31ac1d1 |
completed | March 7, 2026, 8:14 a.m. |
Created at: March 6, 2026, 10:01 p.m.