Triple
T36669961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz 7 |
E905383
|
entity |
| Predicate | rendezvousAttemptedWith |
P99111
|
FINISHED |
| Object | Soyuz 8 |
—
|
NE NERFINISHED |
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: Soyuz 8 | Statement: [Soyuz 7, rendezvousAttemptedWith, Soyuz 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rendezvousAttemptedWith Context triple: [Soyuz 7, rendezvousAttemptedWith, Soyuz 8]
-
A.
rendezvousAttemptResult
Indicates the outcome or status of an attempt by entities to meet or rendezvous with each other.
-
B.
rendezvousTarget
Indicates that one entity is designated as the meeting or rendezvous point for another entity.
-
C.
rendezvousWith
Indicates that two or more entities meet or come together at an agreed place and time, often for a specific purpose.
-
D.
rendezvousSystem
Indicates a system or mechanism that coordinates and manages the meeting or docking of two or more entities at a specified place and time.
-
E.
aimedToConnect
chosen
Indicates an intention or effort by one entity to establish a link, relationship, or communication channel with 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_69f76e6f10008190aea41746aa1b186e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.