Triple
T27609779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expedition 1 |
E700280
|
entity |
| Predicate | moduleActivated |
P137167
|
FINISHED |
| Object | Zvezda service module |
—
|
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: Zvezda service module | Statement: [Expedition 1, moduleActivated, Zvezda service module]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moduleActivated Context triple: [Expedition 1, moduleActivated, Zvezda service module]
-
A.
activatedFor
Indicates that something has been enabled, triggered, or made operational specifically on behalf of or in the context of a particular entity or target.
-
B.
issModuleInstalled
chosen
Indicates that a specific software module has been successfully installed and is currently present in the system.
-
C.
extensionOpened
Indicates that a software extension has been activated or launched from its previously closed or inactive state.
-
D.
canBeActivatedFor
Indicates that one entity is capable of being put into an active or operational state by or for another entity.
-
E.
portalActivationItem
Indicates that a specific item is used to activate or open a portal.
- 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6309e79108190a5fa90c4484eeb22 |
completed | May 2, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:10 p.m.