Triple
T197952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voyager 1 |
E4038
|
entity |
| Predicate | communicationSystem |
P2798
|
FINISHED |
| Object | high-gain antenna |
—
|
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: high-gain antenna | Statement: [Voyager 1, communicationSystem, high-gain antenna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communicationSystem Context triple: [Voyager 1, communicationSystem, high-gain antenna]
-
A.
communicationChannel
chosen
Indicates a medium or method through which information is transmitted between parties.
-
B.
communicationMode
Indicates the method or channel through which communication between entities is carried out.
-
C.
appointmentMethod
Indicates how an appointment is arranged, such as the channel, process, or means used to schedule it.
-
D.
socialSystem
Indicates a relationship where entities are organized into a structured set of social roles, norms, and interactions that govern their collective behavior.
-
E.
commands
Indicates that one entity holds authority over another and issues directives or orders that the other is expected to follow.
- 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_69a254bca59881909a15e1496f1508c7 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25be47ea881909c296b30a0d47a65 |
completed | Feb. 28, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69a25b47481c8190add47c641c977bb9 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:44 a.m.