Triple
T38092391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BEAM |
E951147
|
entity |
| Predicate | attachedSegment |
P10139
|
FINISHED |
| Object | US Orbital Segment |
—
|
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: US Orbital Segment | Statement: [BEAM, attachedSegment, US Orbital Segment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attachedSegment Context triple: [BEAM, attachedSegment, US Orbital Segment]
-
A.
rupturedSegmentOf
Indicates that one entity is a segment that has undergone rupture and is part of, or derived from, another entity.
-
B.
attachedTo
chosen
Indicates that one entity is physically or logically fastened, connected, or joined to another entity.
-
C.
intendedSegment
Indicates that one entity is the target or designated recipient segment for another entity (such as a message, offer, or action).
-
D.
trackedSegment
Indicates that a specific segment or portion of something (such as a path, process, or sequence) is being monitored, recorded, or followed over time.
-
E.
sisterSegment
Indicates that two segments share a common parent or grouping and are considered parallel or equivalent parts within that larger structure.
- 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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: May 3, 2026, 4:21 p.m.