Triple
T30218520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ULF1.1 |
E768273
|
entity |
| Predicate | issAssemblySequence |
P168992
|
FINISHED |
| Object | ULF series |
—
|
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: ULF series | Statement: [ULF1.1, issAssemblySequence, ULF series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issAssemblySequence Context triple: [ULF1.1, issAssemblySequence, ULF series]
-
A.
issAssemblyFlight
Indicates that a flight is part of the International Space Station’s assembly or construction missions.
-
B.
involvedInComplexAssembly
Indicates that an entity participates in the process of assembling or forming a larger molecular or structural complex.
-
C.
finalAssemblyBy
Indicates that one entity is responsible for performing the last stage of assembling or putting together another entity.
-
D.
traditionalAssembly
Indicates that an entity is created, constructed, or put together using conventional, established methods rather than modern or alternative techniques.
-
E.
coreAssembly
Indicates that an entity is responsible for assembling or integrating the central or primary components of another entity into a complete core unit.
- F. None of above. chosen
Provenance (4 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ff800788190b72b805d7ab44594 |
completed | May 2, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 29, 2026, 7:34 p.m.