Triple
T9754534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AUTO |
E236520
|
entity |
| Predicate | directive |
P37145
|
FINISHED |
| Object | prevent return to Earth |
—
|
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: prevent return to Earth | Statement: [AUTO, directive, prevent return to Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directive Context triple: [AUTO, directive, prevent return to Earth]
-
A.
instruction
chosen
Indicates that one entity provides a directive or order specifying an action that another entity should perform.
-
B.
directed
Indicates that one entity served as the director or guiding authority responsible for overseeing and controlling the actions or production involving another entity.
-
C.
usesDirective
Indicates that one entity applies, references, or relies on a specific directive issued or defined by another entity.
-
D.
designationAct
Indicates an official act by which an authority formally assigns, names, or appoints an entity to a specific role, status, or function.
-
E.
decisionDirection
Indicates the orientation or course (e.g., choice, stance, or path) that a decision takes relative to available options or influencing factors.
- 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_69ca84d4eddc8190996fec1417d2bae8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9fb01ad08190b2435fa505c622bc |
completed | April 1, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69cd03d0772c8190bd1750cf1cfba309 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:24 p.m.