Triple
T7834918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spartan-Halley free-flyer |
E181666
|
entity |
| Predicate | autonomy |
P5082
|
FINISHED |
| Object | autonomous |
—
|
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: autonomous | Statement: [Spartan-Halley free-flyer, autonomy, autonomous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: autonomy Context triple: [Spartan-Halley free-flyer, autonomy, autonomous]
-
A.
grantsOfAutonomy
Indicates that one entity confers a degree of self-governance, independence, or decision-making authority to another entity.
-
B.
autonomyDemand
Indicates a request or assertion by one party to have independent control or self-governance in a situation or relationship.
-
C.
autonomyStatus
chosen
Indicates the degree to which an entity operates independently or with self-governed control, without external direction or intervention.
-
D.
hasLimitedAutonomyIn
Indicates that an entity operates or makes decisions within a domain where its freedom of action is constrained or controlled by another entity or governing context.
-
E.
independenceFrom
Indicates that one entity is not controlled, governed, or significantly influenced 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_69ca8284a25c8190a1a20afad30da792 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb064b872081908e269f4fe1b85436 |
completed | March 30, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69cae91e98988190abd4ece75932c589 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:45 p.m.