Triple
T32040902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AUTO attempts to prevent return to Earth |
E818216
|
entity |
| Predicate | AUTOAction |
P152031
|
FINISHED |
| Object | defiesCaptainOrders |
—
|
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: defiesCaptainOrders | Statement: [AUTO attempts to prevent return to Earth, AUTOAction, defiesCaptainOrders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AUTOAction Context triple: [AUTO attempts to prevent return to Earth, AUTOAction, defiesCaptainOrders]
-
A.
actionBy
chosen
Indicates that a particular action is performed or carried out by a specified agent or entity.
-
B.
FAAction
Indicates an action or operation performed by one entity that affects or involves another entity.
-
C.
fromAct
Indicates that an entity originates from, is produced by, or results from a specified action or event.
-
D.
commonAction
Indicates that multiple entities participate in or perform the same action or activity.
-
E.
coreAction
Indicates the primary or central action that defines the main relationship or event occurring between the involved entities.
- 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_69f6b49ee3788190bfcfaaf7e11211c0 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b154b3dc819087115f5f63f7b00f |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:19 a.m.