Triple
T38044811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Axiom Space |
E949587
|
entity |
| Predicate | organizedMission |
P123304
|
FINISHED |
| Object | Axiom Mission 1 |
—
|
NE NERFINISHED |
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: Axiom Mission 1 | Statement: [Axiom Space, organizedMission, Axiom Mission 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizedMission Context triple: [Axiom Space, organizedMission, Axiom Mission 1]
-
A.
segmentMission
Indicates that a specific mission is associated with, assigned to, or carried out within a particular segment or phase.
-
B.
publicMission
Indicates that an entity carries out a mission or activity intended for the general public or serving public interests.
-
C.
organizationMissionSupported
Indicates that an organization’s mission is actively backed, promoted, or furthered by another entity or activity.
-
D.
missionIn
Indicates that an entity participates in, is assigned to, or occurs within a particular mission.
-
E.
organizedExpedition
chosen
Indicates that an entity planned, coordinated, and arranged the details of an expedition or journey.
- 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_69f76eff0bb0819084bc4e63997bd039 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
Created at: May 3, 2026, 4:20 p.m.