Triple
T23477038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-75 |
E570291
|
entity |
| Predicate | tetherBreakDistance |
P79700
|
FINISHED |
| Object | 19.7 kilometers deployed |
—
|
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: 19.7 kilometers deployed | Statement: [STS-75, tetherBreakDistance, 19.7 kilometers deployed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tetherBreakDistance Context triple: [STS-75, tetherBreakDistance, 19.7 kilometers deployed]
-
A.
supportsTransmissionDistance
Indicates that one entity enables or is compatible with the transmission of signals or data over a specified distance.
-
B.
hasLongerReachThan
Indicates that one entity can extend, influence, or physically reach farther than another entity.
-
C.
hasTrailDistanceToFootbridge
Indicates the length of the trail segment separating a given location or feature from a specified footbridge.
-
D.
tieBreakerMetric
Indicates a metric used to resolve ties when primary comparison criteria result in equal values.
-
E.
wireDistance
chosen
Indicates the physical separation or length of wire between two connected points or components.
- 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_69e245af8a88819084f2704f6d265a92 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a74dbea8819085ca84391039e7f7 |
completed | April 29, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:01 p.m.