Triple
T35250344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voyager 6 |
E1018076
|
entity |
| Predicate | gainsProperty |
P171022
|
FINISHED |
| Object | self-awareness |
—
|
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: self-awareness | Statement: [Voyager 6, gainsProperty, self-awareness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gainsProperty Context triple: [Voyager 6, gainsProperty, self-awareness]
-
A.
gainedBy
Indicates that something comes to possess, obtain, or receive something else as a result of an action, process, or event.
-
B.
gainsAbility
chosen
Indicates that one entity comes to acquire or develop a new ability as a result of another entity or event.
-
C.
changesProperty
Indicates that one entity causes a change in a specific property or attribute of another entity.
-
D.
growthProperty
Indicates that one entity characterizes, constrains, or quantifies how another entity grows or changes in magnitude over some parameter (such as time, size, or input).
-
E.
gaugeProperty
Indicates a relationship where a gauge measures, reflects, or represents a specific property or attribute of something.
- 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_69f76de407d081909dfc3c419817ae93 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.