Triple
T30218521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ULF1.1 |
E768273
|
entity |
| Predicate | issAssemblySequencePosition |
P137790
|
FINISHED |
| Object | ULF1.1 segment |
—
|
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: ULF1.1 segment | Statement: [ULF1.1, issAssemblySequencePosition, ULF1.1 segment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issAssemblySequencePosition Context triple: [ULF1.1, issAssemblySequencePosition, ULF1.1 segment]
-
A.
issAssemblySequence
Indicates that one entity specifies the ordered sequence of assembly steps or components required to construct another entity.
-
B.
issAssemblyFlight
Indicates that a flight is part of the International Space Station’s assembly or construction missions.
-
C.
locationOfAssembly
Indicates the place where a group, object, or structure is put together, constructed, or assembled.
-
D.
roleInAssembly
Indicates the specific function, position, or responsibility an entity holds within a particular assembly or gathering.
-
E.
hasSequencePosition
chosen
Indicates that an element occupies a specific position or order within a sequence.
- 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_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_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:34 p.m.