Triple
T32040673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Axiom autopilot |
E818210
|
entity |
| Predicate | followsDirective |
P55040
|
FINISHED |
| Object | keep humans aboard the Axiom |
—
|
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: keep humans aboard the Axiom | Statement: [Axiom autopilot, followsDirective, keep humans aboard the Axiom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsDirective Context triple: [Axiom autopilot, followsDirective, keep humans aboard the Axiom]
-
A.
follows
Indicates that one entity comes after, moves behind, or acts in accordance with another entity in time, space, or sequence.
-
B.
followsIn
Indicates that one entity comes after or succeeds another in a sequence, order, or progression.
-
C.
followsTo
Indicates that one entity moves or proceeds behind another entity toward a specific destination or target.
-
D.
followsRouteOf
Indicates that one entity travels along the same path or route that another entity takes or has taken.
-
E.
followsObjective
chosen
Indicates that one entity pursues, adheres to, or acts in accordance with the goal, plan, or objective defined by another entity.
- 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_69f348fcfb648190859f6be5e04b7cfe |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fddd373cdc8190be1b12e70e4deb1f |
completed | May 8, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69fddc6915a88190ad41e379aa3ede13 |
completed | May 8, 2026, 12:51 p.m. |
Created at: May 1, 2026, 12:19 a.m.