Triple
T34982311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federation–Cardassian border realignment |
E1008847
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | interstellar agreement |
C824
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: interstellar agreement Context triple: [Federation–Cardassian border realignment, instanceOf, interstellar agreement]
-
A.
interstellar state
An interstellar state is a political entity whose authority, population, and infrastructure extend across multiple star systems, governing spacefaring societies and their interplanetary territories.
-
B.
international agreement
chosen
An international agreement is a formal, negotiated arrangement between two or more sovereign states or international organizations that creates binding obligations under international law.
-
C.
interstellar message
An interstellar message is a deliberately crafted communication intended to be transmitted across the vast distances between star systems, typically encoding information about its senders, their environment, or their technology in a form that might be interpretable by extraterrestrial intelligences.
-
D.
interstellar bubble
An interstellar bubble is a vast, low-density cavity in the interstellar medium carved out by the stellar winds and radiation of massive stars, often bounded by a shell of compressed gas and dust.
-
E.
interstellar vessel
An interstellar vessel is a spacecraft designed for sustained travel between star systems, supporting propulsion, navigation, life support, and shielding over vast interstellar distances.
- F. None of above.
Provenance (1 batch)
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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.