Triple
T7918750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unity |
E183890
|
entity |
| Predicate | joinedWith |
P70673
|
FINISHED |
| Object | Zarya during STS-88 mission |
—
|
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: Zarya during STS-88 mission | Statement: [Unity, joinedWith, Zarya during STS-88 mission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: joinedWith Context triple: [Unity, joinedWith, Zarya during STS-88 mission]
-
A.
joinedPluralityBy
Indicates that multiple entities collectively became members or participants of the same group, organization, or event through a shared act of joining.
-
B.
joinedByInPart
Indicates that multiple entities are connected or associated together through a shared participation in a specific part or component of something.
-
C.
combinedIn
chosen
Indicates that two or more entities are merged, joined, or used together to form a single combined whole or context.
-
D.
heldTogetherWith
Indicates that two or more entities are physically joined or kept in contact by some binding, fastening, or cohesive force.
-
E.
joinedByInJudgment
Indicates that one entity participates together with another entity in issuing or sharing a particular judgment or decision.
- 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_69ca828efbe48190bd48482650182e79 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a8fbbb48190b50def4941761a31 |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae9316e98819080be7bf1a6ff92f1 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:05 p.m.